Spring Boot VS Grails

- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...

I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.

https://github.com/spring-projects/spring-boot/pull/39754/co...

If you’re currently running with an earlier version of Spring Boot, I recommend that you upgrade to Spring Boot 2.7 before migrating to Spring Boot 3.0. It minimizes compatibility issues as much as possible.

Okay, we need to build the game? No problem, we will use Spring Boot and Swing!

It's weird that some people including you directly attack my competence. As a power user you should have plenty of experience getting something to work that is not properly document, does not work how the documentation promised it to, or has weird problems on top of it. Look at idiotic things like this:

https://github.com/spring-projects/spring-boot/issues/33044

Take any similar issue and you'll see a bunch of people who try to find a solution for them because they just aren't repeatable at all. The underlying issue is the auto configuration doing things you can't follow quite properly. It's like it wasn't mean to be understood. Issues like the one I linked above also show me that the spring dev crowd also doesn't understand the ecosystem anymore. The problem is complexity and automagic.

An interested reader can decide for themselves:

https://github.com/spring-projects/spring-boot/tree/main/spr...

Explicitly decoding URL query parameters occurs less often because many frameworks, including Spring Boot, handle decoding automatically.

And frameworks like Grails build conventions and helpers on top of Spring.

I don't have any direct experience and am only suggesting it because you mentioned RoR...But Grails (https://grails.org/) is basically the JVM version of RoR (Groovy on Rails -> Grails).

Grails - Spring under the hood. Much less boilerplate. Opinionated, which helps keep things consistent. Uses Spring-Security plugin for authentication.

Also, Grails, which a Rails like framework build on Groovy, a JVM scripting language.

Any JVM language to the rescue here? There’s one, but it’s not the one you’re thinking about. In a sign that this index may not accurately reflect our project reality, Groovy saw a meteoric rise of 0.86% to 1.04% last year! That was good for place 17. Yep, Groovy! Are people writing Gradle plugins in Groovy? Or is Grails having a resurgence? I’m as baffled as you are.