5 ms·

Migrating from Java 8/11 to Java 21, and Spring Boot 2 to Spring Boot 3.2

19 points by shardullavekar 3y ago

TexanFeller 3y ago
[flagged]
- slively 3y ago
  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.
  - wizerdrobe 3y ago
    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.
    - pjmlp 3y ago
      .NET is also quite comparable. 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.
- gloryjulio 3y ago
  Why not? Btw it's Spring Boot, not Spring. It's a nice streamlined package which is much more pleasant to use
- kdtsh 3y ago
  Why? What would you talk about instead?
- jmpavlec 3y ago
  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.
- pjmlp 3y ago
  It kills me that in 2024 people keep hating framworks, while reinventing them badly.
  - ysleepy 3y ago
    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.
- bzzzt 3y ago
  > 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.

TexanFeller 3y ago

[flagged]

slively 3y ago
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.
- wizerdrobe 3y ago
  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.
  - pjmlp 3y ago
    .NET is also quite comparable. 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.
gloryjulio 3y ago
Why not? Btw it's Spring Boot, not Spring. It's a nice streamlined package which is much more pleasant to use
kdtsh 3y ago
Why? What would you talk about instead?
jmpavlec 3y ago
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.
pjmlp 3y ago
It kills me that in 2024 people keep hating framworks, while reinventing them badly.
- ysleepy 3y ago
  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.
bzzzt 3y ago
> 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.