buherator
buherator
The documentation is a mess. I can't find a single, complete tutorial about the most basic things like database access. If something doesn't work, it's impossible to debug the "framework magic", you have to guess. Oh and you can't find useful guidance by googling, because everything can be performed numerous ways, so there is 0 chance you'll find the exact problem you are facing.
How do people manage to get this shit work at all?
#java #spring #springboot
2
0
2
author_is_stribika
stribika@cybervillains.com@buherator They made dependency injection easy, and then slowly added everything and the kitchen sink. It's still possible to use just for DI, but adding dependency on another spring module is often the path of least resistance. Until we ended up with Spring Boot, a framework to configure the framework, because it's way to complicated.
0
0
1
- they were "old" (2022)
- there was no hint of an API change in the errors or in the official docs
- dependency injection made the bug *impossible* to debug, even though I'm the kind of person who will dive into raw jdb/JDWP if I have to.
Based on this job security must be an important pillar here... I wonder if you see any alternatives (for the whole framework or even for Spring Security) worth considering/gaining momentum?
1
0
0
author_is_stribika
stribika@cybervillains.com@buherator @wiverson
The idea behind DI is that it makes writing tests easier, so the need to debug is less frequent. It's pretty much the core of spring, any other feature depends on it. But if you *only* want that, there are light weight frameworks like Guice.
I don't know any decent spring security replacements, and if you need it, why not just use the rest of spring. For auth it's pretty OK, but for access control it's more trouble than it's worth.
0
0
1
@buherator lol. There is a guide which explains how to use databases with spring boot. if that doesn't work for you, maybe tell us what exactly is the problem?
0
0
0