This looks like not a reskin of an existing FreeBSD or Linux windows system, but an actual reimplementation of macOS. Very interesting if they can pull it off!
I wonder though, why start with old Objective-C cocoa APIs instead of Swift?
You can customize which region you want your functions to run in that handle server-rendering. Currently running multi-region functions (lambdas) requires an enterprise plan, but using Edge Functions, they can be multi-region or global if you’d prefer. It depends on where your data is and if it’s replicated.
You are correct that Vercel serves requests from the region closest to the visitor. Our servers automatically scale (serverless) so it doesn’t need to balance across regions. However, in an instance of downtime, Vercel would route traffic to the next nearest region.
Beyond the pedantic distinction, is there any real point to not calling "at-least-once delivery with idempotent processing" exactly-once processing? I can't imagine that any external observers would be able to tell.
Litestream author here. This is on the staging site for the docs for the upcoming v0.4.0 release. I’d love to hear feedback from anyone who wants to kick the tires before the release. Thanks!
The way it happens always: many people working to a solution, not agreeing on one and then comprising on something in the middle, even if it makes no sense.
> If the whole point of being a spy is that nobody knows who you really are and no one can ever find out, how exactly are you supposed to achieve this level of anonymity when you’ve flung untold reams of identifiable content across the digital world?
When everyone has an online presence, the absence of such a presence raises huge red flags. I would expect every spy on earth nowadays has tons of pictures on social media showing them having fun with their friends, cool vacations they've been on, selfies with famous people they've met. So long as they don't tweet something dumb like "CIA's sending me to Belarus #Coup2022", anyone looking at their profile will most likely see a normal person who is probably here for normal reasons. Sure maybe if they went over the profile with a fine tooth comb they'ed notice some things that don't add up, but there isn't a reason to look closer. On the other hand the person without a social media gets scrutinized, and regardless of when you were born there is information on you out there that a sufficiently motivated individual can find.
Almost 20 years of professional experience here: I fully agree with this list. I even want to add a few things:
> Clever code isn't usually good code. Clarity trumps all other concerns.
My measurement is "simple and clean" code. Is it simple and clean? No? make it so!
> After performing over 100 interviews: interviewing is thoroughly broken. I also have no idea how to actually make it better.
If a good developer you know, recommends someone they worked with: It's almost an instant hire. But for the rest, yeah, it's incredibly tough.
One last thing I like to remind myself: "Good enough is always good enough". Sometimes "good enough" has a low bar, sometimes high. You always need to reach it, but never want to go too far above it.
Car purchase includes a huge amount of 'non rational actor' decision making. I like old jaguars. Walnut burr, doors that go "thunk" -in every sense (fuel economy, NCAP, reliability) they are irrational purchase: I still love them. And the Citroen DS19.
EVs are in a segment with high discretionary spend. Choices in discretionary spending are notoriously bound up in non-rational choices: I could invest in diamonds, or snort it as coke, or fly to the bahamas in a helicopter is totally different lifestyle choices to "I need to get to Walmart at 3am for diapers, and I cannot afford to pay for more than basic AirConditioning"
When EVs are in the segment of rational-decision bound purchases, when they are "boring" I will deem them to have succeeded.
As long as the competition is Fiskar, not VW, and Not the Ioniq, or other Japanese low-end EV, its not baked yet.
The low-end EV have to get about 50% more efficiency and drop price about 30%. There really is a sweet spot in most people's disposable income and on-road costs and range anxiety (also a highly irrational place btw) which is just around the corner:
under $20,000 in any local economy
over 300km range in real-life
chargeable for usable amounts (10%? 20%?) in under 15min
I wonder though, why start with old Objective-C cocoa APIs instead of Swift?