No, back in the day C was used for everything. Vim was not written in C because it needed to wring every last bit of performance out of text editing.
Rewriting everything in rust "for memory-safety" is a false tradeoff given the millions of lines of C code out there and the fact that rewrites always introduce new bugs.
There's a contingent of rust fans that show up on every story about C – their premise is that C code is unsafe and most safety-critical C code should be rewritten in rust.
Fil-C is new and is a viable competitor to rust, that's why you're hearing all asides about tiny niches, unacceptable performance degradation, etc.
Well the problem with SF is less density and more than half of it is single-family home neighborhoods with zero amenities.
Anti-growth people will point to neighborhoods like Glen Park, NoPa and Noe as "SF" while forgetting most of the surface area of the city is empty neighborhoods like Parkside, Mt Davidson Manor, etc.
It really feels like all these concerns about semantic everything belong to a previous era of the web. I remember arguing with people 20 years ago who believed RDF and the semantic web was going to take over, but the use cases never materialized.
This is just pushing the externalities to the residents. It takes several months for airbnbs to get banned, and it's tough for smaller cities to get the bans enforced.
There must be a better answer than "pass a law so the american multinational does a better job at regulating its rentals"
It could also be misguided security guidelines – because of things like caller id spoofing where scammers would spoof one of their actual numbers to lull people into a false sense of security
The competitive advantage is not physiological. Following your reasoning, that'd mean an F1 driver's competitive advantage is how fast they can push the pedals to get to 300kmph.
The real advantage is how fast you can navigate dangerous mountain roads which are narrow and have many hairpin turns.
This is very wrong. These guys go downhill on small country roads very fast – sometimes over 100 kmh. You need deep riding skills to handle these speeds without getting injured.
This is very unhelpful. There's a difference between "someone fatfingered a command and brought this mysql machine down" and "our cloud provider shut down a core feature for our account".
When you design a new system do you plan for S3 to go down for more than a day? Do you have a fleet of offsite machines to smoothly transition to? If not, why not?