I spent untold hours and years mastering inversion of control and late-binding and all those design patterns that were SOOOOO important for interviews only to never really utilize all that stuff because once the apps were built, they rarely, if ever, got reconfigured to do something besides the exact thing they were built for. We might as well have not bothered with any of it and just wrote modular, testable non-OOP code and called it a day. After just about 25 years, I look back at all the time I spent using Spring Framework, Struts, and older products and just kind of shake my head. It was all someone else's money making scheme.
I'm also reminded about the time that Tomcat stopped being an application you deploy to and just being an embedded library in the runtime! It was like the collective light went on that Web containers were just a sham. That didn't prevent employers from forcing me to keep using Websphere/WAS because "they paid for that and by god they're going to use it!" Meanwhile it was totally obsolete as docker containers just swept them all by the wayside.
I wonder what "Webshere admins" are doing these days? That was once a lucrative role to be able to manage those Jython configs, lol.
My criticism of the JVM is that it is no longer useful because we don't do portability using that mechanism anymore. We build applications that run in containers and can be compiled in the exact type of environment they are going to run inside of and we control all of that. The old days of Sun Microsystems and Java needing to run on Solaris, DEC, HP, maybe SGI, and later Linux, are LOOOOOOONG gone. And yet here we still are with portability inside our portability for ancient reasons.
I haven't use Go since 2024, but I was going to say something similar--seems like I was pretty happy doing all my Functional style coding in Go. The problem for me was the client didn't want us to use it. We were given the choice between Java (ugh) and Python to build APIs. We chose Python because I cross my arms and bite my lip and refuse to write anymore Java in these days of containers as the portability. I never really liked Java, or maybe I never really like the kinds of jobs you get using Java? <-- that
I have only used Kotlin on the JVM. You're saying there's a way to avoid the JVM and build binaries with it? Gotta go look that up. The problem with Kotlin is not the language but finding jobs using it can be spotty. "Kotlin specialist" isn't really a thing at all. You can find more Golang and Python jobs than Kotlin.
But it's not--Go is a thoroughly modern language, minus a few things as noted in this discussion. But it's very and I've written quite a few APIs for corporate clients using it and they are doing great.
This is a facile approach to making an argument against US Healthcare--far too simplistic, imho. There are plenty of nations with socialism/communism where healthcare is either non-existent or impossible to get because of rationing. So it's not like that's some terribly invalid argument. Further, even with the more "civilized" Western nations, the cracks in those socialized systems are showing--the UK, Canada, and others. Finally, the countries with the allegedly great healthcare are pretty small compared to the USA. I can't speak for India, of course, but I kind of think that a nation that lacks flush toilets for a large percentage of its population would also be suspect in terms of broad applicability around what was stated. In simpler terms: If you're wealthy, you can get great healthcare almost anywhere. The US has its lumps, but there is no waiting for necessary treatments and while insurance is expensive, so is healthcare.
I guess I'm also happy that our government doesn't run it because just regulating it as much as has been done has led to what we experience today. Is greedy profiteering built in to the system? Undoubtably. But there are serious risks to reforming such a complex system.
I disagree. I think if we stop using oil and gas, we fall into a new dark ages pretty fast and half or more of all humans will die. Is that what you intend?
We have more options than just (instantly) stop using oil and gas and those options would have been far more easy to implement had we been doing them for the last 50 years instead of arguing about if climate change is happening, and now, if humans have caused climate change.
These other options require resources and time to implement, and the political capital required to make that happen has been and will be increased because of the aforementioned 'debates'.
Sure, but maybe we should have been transitioning our communities 20-30 years ago away from encouraging people to hop in a massive SUV getting 17MPG just to go get a loaf of bread. Maybe we should have been working towards reducing our carbon impact in sane, practical ways many decades ago instead of having our heads buried in the sand for so long.
It will always be up for debate, though. That's the thing--unless you are an absolutist, you will understand that scientific inquiry is a never-ending process and that all the "it's settled science" people don't seem to understand that at one time humans thought the earth was the center of the universe and that applying leeches to people helped remove the "ill humours" they were suffering form. All of that was also "settled science." Until it wasn't.
I'm also reminded about the time that Tomcat stopped being an application you deploy to and just being an embedded library in the runtime! It was like the collective light went on that Web containers were just a sham. That didn't prevent employers from forcing me to keep using Websphere/WAS because "they paid for that and by god they're going to use it!" Meanwhile it was totally obsolete as docker containers just swept them all by the wayside.
I wonder what "Webshere admins" are doing these days? That was once a lucrative role to be able to manage those Jython configs, lol.
reply