I think this is probably the most salient point. C/Rust then Java. I don't know why people hate on Java so much. And I think C lives fine along side Rust.
> Java forces OOP and it's verbosity is worse than COBOL.
Java doesn't force OOP in any meaningful way. I mean it does, in that you need to wrap all code in a class, but that's a non-issue (one line of code at the top and a closing bracket). You can write Java code where all functions are static and do nothing is object-oriented, when that's the best match for your needs.
On verbosity, you can latch on to the ConstructorAccessorMapFieldGetterFactorySingleton nonsense if you want but that's on you. Nothing in the Java language forces that on anyone. Having been writing Java code since 1996 I've never written such code.
Java is based on Objective-C without any of the nice flexibility, doesn't have value types, has C-like numeric types except they're less flexible yet not any safer, and its culture thinks you organize code by putting it into 6+ layers of namespaces inside other namespaces.
My rule is that languages are good if they have value types, which explains why PHP is good.
Having cut my teeth in Z80 Assembly, I could never understand people's aversion to pointers. You cannot do anything of any practical use, on hardware, without them.
templates are one of the best features of c++. they're complicated because they're powerful. they certainly aren't perfect, but you won't find anything like them in other popular languages.
As an older dev, screw those older devs that 'roast your code'.
The really good ones won't do that. The ones that do suffer from some weak superiority complex. I had three awesome mentors when I started writing C, and a couple great mentors when I did what little C++ work that I had to do.
The only scold I ever dealt with wrote overly wrought, overly complex crap. Kitchen sink patterns to handle any possible future variation, instead of solving the problem at hand.
Stay away from people like that, they'll just turn you into the same old grouch.
As an embedded systems developer for 38 years, with 26 years writing for small threaded RTOS, including 16 and 32 bit DSPs, and the remainder being platform work on QNX Neutrino, NetBSD, and Linux, most of my code has been K&R, then ANSI C.
A very small amount of C++, but by comparison, a very small amount.
Everything else, Shell, Perl, Python, is a shadow by comparison.
My commute to work is very predictable, but the commute home is not. I always use Google maps driving home, even though it is only 27 miles, because Gmaps will direct me to alternate routes if there is a traffic tie up on my usual route home. This has saved me literally days of time over my years of commuting.
This mirrors my experience directly. Before smart phones, I found TomTom to be more user friendly than competitors, but they were slow to boot up, the battery was only useful for providing clean power vs the car electrical system. I tried using my TomTom for walking Navigation. The battery lasted long enough to reach my destination, but luckily I remembered my way back to the parking lot after, because the battery did not make it.
Google Maps on my phone works fine, and on my current Pixel 5A, I can navigate off battery for a three or four hours. Plenty of walking time to hit multiple points in a day of walking.
Maybe some day the TomTom app will be competitive with Google maps, but for now, Google maps is the reference by which all other mapping will be judged.
