Renting a car is more of a pain these days. I find I actually have to learn how that car "likes its buttons". I don't remember having to look at a physical gear shifter to know it's in drive/reverse, etc. Now I have to see if some light is on. It must have been obvious to Human Factors folks from the outset that this was all a waste of time.
Long-term maybe we won't care about code because AI will just maintain it itself. Before that day comes, don't you want a coding language that isn't opinionated, but rather able to describe the problem at hand in the most understandable way possible (to a human)?
I find it annoying in Java when uppercase is used because its an acronym. URL or UUID. No man, just Url/Uuid. No need to yell just because its an acronym.
My OO projects were usually in Java with a DB. They all ran afoul of what Martin Fowler calls the Anemic Domain Model. Basically your objects are data-only, so there's no benefit. In addition Spring injection became ubiquitous, and further killed objects with behavior. The only project using a DB and had objects with behavior was an old one that happened to use TopLink as an OR mapping.
"One can even conjecture that LISP owes its survival specifically to the fact that its programs are lists, which everyone, including me, has regarded as a disadvantage"
Not the first time someone didn't realize what they had.
Java didn't exist when I originally wrote C++ code. When it did come around it was easily 4x improvement for a good amount of development (eg. enterprise software). I think you need like 4x+ to be worth switching, and I don't see that between many languages. I do see it between libraries/frameworks though.
I think a lot of the problem of switching isn't so much the language, but relearning all the undocumented lessons that were learned the hard way the first time around.
Work gave me a 5k monitor to use at home. I set it up dual monitor with my cheap-o monitor. Had to upgrade that as it looked awful. But now maybe better for my eyes?
They wouldn't want even the appearance of it being an Apple product running crap on it. If there was some way to completely distance themselves from it, maybe, but pretty much a non-starter.
Programmers are notoriously bad about making estimates. Sure it sped something up 10x, but did you consider those 10 tries using AI that didn't pan out? You're not even breaking even, you are losing time.