3 ms·
Lately I have insight similar to 'what hardware improvements give, software bloat take it away', 'what JDK platforms give third party Java frameworks take it aw
by geodel 5y ago
Lately I have insight similar to 'what hardware improvements give, software bloat take it away', 'what JDK platforms give third party Java frameworks take it away.
I have this misfortune of dealing daily with a nasty Java framework which converts compile time errors into runtime errors, single error trace with multiple stack traces , most of them being from framework itself.
One thing that might improve situation is server side libraries instead of framework. However AFAIK there is nothing like that in Java world. Everything is bound to Servlet API at lowest level and app server/frameworks on top of it.
- treypitt 5y agowhat was the framework, if you don't mind sharing?
- geodel 5y agoSpringBoot.
- shipp02 5y agoWhat do you think of vertx. It seems pretty lightweight set of server side libraries along with activej which also focuses on speed.
- vbezhenar 5y agoThere are plenty of frameworks. Check out Helidon, Quarkus, Micronaut as examples of modern frameworks. You might like them. They’re not bound to servlet API.
- geodel 5y agoI should have clarified one unfortunate part of this is enterprise diktat. So I stand no chance when a snake oil salesman from VMWare tells CIO on which framework they provide support for.
- valbaca 5y agoDagger 2 is a fantastic lightweight DI framework that gets out of your way and keeps the errors to compile-time https://github.com/google/dagger https://github.com/google/dagger After that you can throw in whatever libraries you want, dagger doesn't care.