I also don't think that men should be given a wife by the state though...
Yes, because the people getting cars on payments have tons of cash lying around.
People who have money, lease. That allows you to exit quickly, and interest rates are cheap, you don't have to tie up your own liquidity.
People who have less money, but are sensible with it, pay cash. That allows you to never be stuck with a car payment you can't afford, and you get to keep your car if something bad happens to your finances.
People who don't have money, or have some money and want to live like they have more of it, get car loans. Unfortunately, some people can't avoid them because they truly don't have even the "50% less" lying around. Car loans are predatory, particularly in the US it seems, and these will fuck you up, causing a cycle where once you've paid off your car, it's not got much life left, or at least, you'd need a slightly larger emergency repair budget lying around, so people tend to get newer cars on new loans.
If the car has a turbo and direct injection and you go by oil color, you barely get off the driveway before having to change it. Oil goes black in under 100 miles. Doesn't mean it stops lubricating, these cars specify oils that technically can do 30k+ miles in some cases and then have you changing the oil at ~15k miles. I still keep around 6-10k myself (10-15k km really, but I be using miles for your benefit here).
Of course, I don't use cheap or low quality oils. I keep to Motul most of the time.
EVs have to be legislated into being the only choice anyway. There's no way around it, they're unfortunately inferior for a lot of people's use cases still. We've grown accustomed to the energy density of fossil fuels and being able to keep cars running out of warranty. A quick look at the replacement battery cost of an original Audi E-Tron will reveal that at this point, EVs are expensive paper weights once out of warranty.
If you have the stricter training and policing, you still can improve safety by introducing speed limits.
What is going to be the excuse for keeping the stricter training and near authoritarian policing if there are speed limits? Nearly no other country is this anal about who can and can't drive on their roads. Maybe Singapore, since they require you to be a millionaire to even get a car.
Ah yes, learn Zangendeutsch for make benefit homeland
I think everyone wants to make good software, except upper level management that only cares about the money. But in some companies, your boss or your boss's boss has some kind of feature roadmap and they get their asses chewed off if that is not met.
I honestly think most people WANT to do good work. But ain't nobody going to work overtime to deliver a better product with unreasonable timelines. Not unless there's a heavy stock option plan and you're in a startup where your input actually changes things.
To your edit: that's one of top 3 reasons I moved to iOS and while there are annoyances, overall I've been happy with it for 3 years. Not suggesting everyone should switch but if you're tired of tinkering, it's a good option.
I don't think it's only a metaphor for war but also a literal depiction of how duels sometimes took place? I do believe that seconds sometimes took the places of the duellants.
This was more than 20 years ago though
I'll show myself out
When possible, use open source software that isn't developed by commercial entities (yes that also disqualifies all real browsers available - maybe Ladybird will be different? But then the specs themselves for the web are so bloated it takes too long to implement them and you have to cut corners).
Thing with for-profit development is that micro-optimizations don't make fiscal sense. Say it takes 10 seconds for an API call. That's too long if it's supposed to be an interactive website! You spend 4 hours getting 9 seconds off by improving multiple problematic methods. Now the next 900 milliseconds? Maybe that'll take you 10 hours. Fun? Absolutely, I live for that shit. But in most commercial environments this would be considered a waste of time because I could spend it doing something more impactful.
And anything being twice as fast or memory efficient is usually not noticeable. If you're going to optimize something, it should be at least an order of magnitude. Therefore everything but low hanging fruits often gets ignored. Usually it's a case of reconsidering your data structures to be able to use better algorithms, or reconsidering the business requirements to get rid of some processing that could be avoided. The former requires architectural insight not every developer has, plus agreement among devs. The latter may require outright navigating office politics to get product team to drop some low business impact feature requirement that has high impact on performance.
Man when you're talking about the "goeiness" of a vegetable, I can see how a lot of people would be turned off by it.