gs-spring-boot VS Spring Boot

You're welcome. You can do this fairly easily with straight java SE, but once you've done that take look at what Spring has to offer, in particular Spring Boot. Inversion of Control and Dependency Injection are super powerful!

You can try the official documentation on https://spring.io/guides/gs/spring-boot/ There are courses as well. Also you can check out https://www.baeldung.com/spring-boot

Spring does have a broilerplate "get it up and running" project. Go to start.sprint.io , configure whichever stuff you will need, download the project, import it in your IntelliJ, read and implement https://spring.io/guides/gs/spring-boot/ , then run it.

Soring's own guides are pretty good to be honest. https://spring.io/guides/gs/spring-boot/

Not necessarily a book recommendation but I’m a strong believer in actually implementing a project to learn about the tech stack. Spring has a great tutorial: https://spring.io/guides/gs/spring-boot/

Their docs are pretty complete. Here is an example with start to finish: https://spring.io/guides/gs/spring-boot/ It says you only need 15min and some libs.

Spring has a guide.

i use java with spring boot (link), also look up "MVC web development", i use thymeleaf in the html as part of the MVC approach. (i use maven to manage the packages.)

- 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.