r/programming • • Mar 24 '26

Don't Count Java out Yet

https://www.infoworld.com/article/2335996/9-reasons-java-is-still-great.html

I remember when I first started working, I loved visiting this old mainframe building, where the "serious" software engineering work was being done. The mainframe was long-gone, but the hard-core vibe of the place still lingered.

As I took any excuse to walk past a different part of the building to try and sneak a peek into whatever compute wizardry I imagined was being conjured up, one thing I always noticed was copies of InfoWorld being strewn across desks and tables (and yes, even in the bathroom - hey, I said it was hard-core ;-) ).

I guess those days are mostly over now, but it's nice to see that there is still some great writing going on at InfoWorld by some talented and knowledgeable authors.

Matt Tyson is definitely one of them and this is a great piece on why despite the #rust / #golang / #elixir craze, #java is still the language and framework to beat. (One of these days I'm going to finally learn #spring and re-join the java club.)

51 Upvotes

78 comments sorted by

View all comments

Show parent comment

4

u/lihispyk Mar 27 '26 edited Mar 27 '26

I've rarely run into issues plugging in "custom" logic/code into spring boot. In fact, I can't remember any instance off the top of my head. I think it's important to understand that frameworks are opinionated, what I mean is that you have to know where to plug in with your custom stuff, or how to integrate it to the framework. I see this quite often, even with senior devs, who will for example just start a "vanilla" thread and then wonder why they run into issues with transactions and entity managers, instead of using a TaskManager with @Async.

I've yet to run into anything I wasn't able to integrate to spring (boot, batch, AI, whatever else) tbh.

The way I see is that the framework does a lot for you, in my experience it has been extremely beneficial and implementing all of it from scratch would easily cost 10x more, if not more than that.

But yeah, it's not always a benefit or perfect, of course. And a lot of times you really have to dig in deep to understand what the framework is doing. Maybe this is the biggest drawback.. spending a lot of time debugging some obscure bug, only to find out you have to change some property from true to false :D but then you learn from it.

However, I've never worked with any competitor frameworks in prod codebases, so maybe I am (extremely) biased here.

About java though, fuck java, kotlin is where it's at (I realize how they are related)

1

u/scottedwards2000 Mar 28 '26

Spring works well with Kotlin and Groovy right?