^this!!
critical driveline software should be separate and autonomous from accessories. My ID.4 which I love but admittedly does not have the smoothest accessory software used to crash the heads-up display and with it the air conditioning system. So, while driving in summer rush hour hear I am performing a hard boot on the system swearing my but off.
Playing devils advocate we have a slew of users who want to be able to drive there car with there iphones.
Electric vehicles are silent in the car park, which is a hazard for pedestrians. There's a good argument that cars should make a sound in this situation, so people are aware a car is moving or about to move.
Apart fro that - yes, the lack of noise, vibration and harshness is a big advantage - and also a design problem, because without engine noise rattles and tyre noise become a bigger issue.
That cap is everyone who wants to buy a car, minus a small group of enthusiasts who mostly buy classic cars second hand anyway.
There are many who can't afford electric cars with the range that they need, but technology is quickly solving that issue as battery research and improving mass production reduces costs.
Unlike IMAP, POP allows you to maintain a local copy of your mail, a copy that is isolated from the server.
For many reasons, people prefer that to IMAP or Exchange, which will delete mail from your local cache if it is removed from the server, and accessing that cache independent from the server is also a challenge.
Thankfully, this isn't Gmail dropping POP support for their users. We will still be able to get emails into Thunderbird or Outlook using POP. What is going away is configuring Gmail to use POP to pull emails from other accounts into the Gmail inbox.
LLM-based AI can do some pretty impressive things. It *seems* to answer questions with remarkable accuracy, and it instantly produces code in response to often ridiculously vague input queries:
"Write me an app to track ant farms in Vietnam"
And what do you know? You get something that seems surprisingly useful!
Except that it's all an illusion.
I'm an experienced software developer (25 years now) and I focus on information lifecycle apps targeting workgroups and enterprise - organizations of 50+ people. As I write this, about 20,000 people are concurrently using an app I created.
Over the past year or so, I've been trying to deeply integrate AI into my workflow. It's there when I write code in VSCode, it's there when I write sysadmin/shell code, and it's there when I'm refactoring.
The more I use it, and the "better" it gets, the more frustrating I find it. It's only somewhat useful in the area that most coding projects fail: debugging.
No matter what it seems, LLM-based AI doesn't *understand* anything. It's just an ever-more-clever trickery based on word prediction. As such, it serves only as another abstraction that still must be understood and reviewed by a real person with actual understanding, or the result is untrustable, unstable, and insecure "vibe code" that is largely worthless outside of securing VC funding, which is the thing that AI perhaps does best: help unprepared people get VC funding.
You still need real people to get code you can live with, depend on, and grow with.
"I've seen it. It's rubbish." -- Marvin the Paranoid Android