I recently started a green field project with sprint boot and Kotlin and it’s a joy compared to the many other things I’ve experienced in the last decade. I’m hoping spring remains strong for a while.
To me, it’s not “should I use Spring” but why not? Most frameworks of the same class crudely ape the format. Then the open-source ecosystem of most languages is a ghetto compared to that of Java.
I hate not using it at work but rather Node all the while watching Typescript libraries reinvent the Spring wheel.
Hence when I am not using one, I am doing the other, sometimes with a bit of C++ underneath, unless forced to use another programming stack due to external decisions.
It has worked quite alright for almost 30 years now.
It kills me that this is the top comment which provides no substance to its claim. Personally, I love Spring Boot both at work and in my side projects. Can it be annoying if you get off the main path? Yes. Does it provide a bunch of useful things for most common web flows. Definitely.
Let's hear why you think we shouldn't be talking about it.
Don't conflate a specific criticism with a general one.
I don't necessarily hate frameworks, but I do dislike Spring.
It's a heavyweight framework, an empty project spits out a 50MiB jar that takes like 5s to start, requiring full classpath scanning, bytecode modification and a full DI setup.
There are much more lightweight and friendly approaches, such as some of the microprofile implementations.
A jersey+jetty setup fits into a 5MiB jar and starts in 200ms.
> It kills me that we're still using and talking about Spring in 2024.
If you're not able to reimplement your whole application every few years there's something to be said for a framework that's over 20 years old and still being used.
10 comments
[ 5.1 ms ] story [ 34.9 ms ] threadI hate not using it at work but rather Node all the while watching Typescript libraries reinvent the Spring wheel.
Hence when I am not using one, I am doing the other, sometimes with a bit of C++ underneath, unless forced to use another programming stack due to external decisions.
It has worked quite alright for almost 30 years now.
Let's hear why you think we shouldn't be talking about it.
I don't necessarily hate frameworks, but I do dislike Spring. It's a heavyweight framework, an empty project spits out a 50MiB jar that takes like 5s to start, requiring full classpath scanning, bytecode modification and a full DI setup.
There are much more lightweight and friendly approaches, such as some of the microprofile implementations. A jersey+jetty setup fits into a 5MiB jar and starts in 200ms.
If you're not able to reimplement your whole application every few years there's something to be said for a framework that's over 20 years old and still being used.