I'm not sure that tracks with my experience, plenty of 20-30 year old cars still running around. The people upgrading every few years do it for financial or image reasons rather than because the car stopped working.
Warranty anxiety is probably a big factor too, which could be legislated. Imagine how reliable cars would be if a 30 year warranty on drivetrain components was mandatory.
A quality car will last just about forever if you take care of it, Irv Gordon put 3.2 million miles on his 1966 Volvo and it was still in good shape at the end. But most people don’t maintain a car like that, however an EV has the potential to last like that with almost no maintenance.
I love that the world is loving kei trucks and kei cars right now.
I see them pretty often in Australia which also has an anti yank-tank movement (tongue in cheek name for a big american "truck")
That said our most popular cars are still all three tonne utes or SUVs so it's a small movement.
You are right to note the economic situation being a big part of vehicle decisions. Fuel prices has been a driving force, and image plays a big part too.
I don't think I would be comfortable serving any DB over the internet these days, exploit scanners are so agressand ubiquitous that a breach would feel inevitable.
Not that it is fool proof, but if I am setting up the infrastructure I can probably control where the DB is deployed, so I would colocate it with the application servers on a local network or virtual local network, that is all I would be comfortable with.
Smaller companies necessarily have a small team stretched across broad responsibilities, that usually describes startups. If it's scaling up then yeah, that changes. You want to join small teams for broad experience, startup or regular business.
One of the reasons an LSP is so useful is that it does not fabricate anything. If my LSP can't tell me something, it means it doesn't exist or I haven't defined it.
In some ways it helps against code being too magic as well, if my LSP can't understand what's happening in the code it is probably because of a magic string, hidden reference or hidden dependency. If you're in a loosely typed language, it also helps spot when you've got some type shenanigans happening.
All of this is instantaneous, and always factual, deterministic, sourced from hard truth.
I do not know how this LLM LSP functions, but instant, always factual and deterministic are not features of LLMs typically.
I'll give it a go though, like I said I don't know what it does under the hood.
It's a corporate feel that comes from a professional setting and lots of risk aversion. That is exactly what LLMs tend to write, so I sometimes catch myself feeling the "LLM ick" but the article was from before the boom.
So I guess it's just the corporate wash cycle, which I am happy to criticize, LLM generated or not.
Warranty anxiety is probably a big factor too, which could be legislated. Imagine how reliable cars would be if a 30 year warranty on drivetrain components was mandatory.
reply