5 ms·

It's so hard to get it configured right that instead of deploying your app to Tomcat, you embed Tomcat in your app and letting the framework deal with the confi

It's so hard to get it configured right that instead of deploying your app to Tomcat, you embed Tomcat in your app and letting the framework deal with the configuration, like in Spring Boot. Of course it means you end up with several dozen/hundred/thousand copies of Tomcat...

mschuster91 4y ago
That's even worse for optimization since now you have to deal with whatever your framework does to get Tomcat up to speed and how to set a configuration option for Tomcat in a way that eventually ends up at the correct place.
geodel 4y ago
And now I have to deal with this supremely crappy Spring Boot which would convert compile time Java errors to runtime exceptions. Turn already verbose 100 lines stack trace from Java into 5000 lines of Spring infested stack trace. I guess I just couldn't praise enough this Spring Boot.
- ElectricalUnion 4y ago
  The only four things that I remember that ended up with crappy run time errors that totally should be compile time Java errors are none specifically related to Spring Boot, they're all generic "Java things": * people using Win boxes for development and therefore antivirus locking files in innoportune times during compilation/packing; * people using the Eclipse Java Compiler, a IDE compiler designed to be useful with bad Java; * people trusting themselves writting XML annotations instead of Java annotations, and not unit testing the code (this lack of unit tests alone probably means the code literally did not even work on their machine); * people using the existential, compile-on-runtime terror that is Java Server Pages.
jayd16 4y ago
>and letting the framework deal with the configuration You could even say that the frameworks put the config on rails. But seriously, just embed the server. Its not a bad deal at all.

5 ms·

It's so hard to get it configured right that instead of deploying your app to Tomcat, you embed Tomcat in your app and letting the framework deal with the confi

by ElectricalUnion 4y ago

mschuster91 4y ago
That's even worse for optimization since now you have to deal with whatever your framework does to get Tomcat up to speed and how to set a configuration option for Tomcat in a way that eventually ends up at the correct place.
geodel 4y ago
And now I have to deal with this supremely crappy Spring Boot which would convert compile time Java errors to runtime exceptions. Turn already verbose 100 lines stack trace from Java into 5000 lines of Spring infested stack trace. I guess I just couldn't praise enough this Spring Boot.
- ElectricalUnion 4y ago
  The only four things that I remember that ended up with crappy run time errors that totally should be compile time Java errors are none specifically related to Spring Boot, they're all generic "Java things": * people using Win boxes for development and therefore antivirus locking files in innoportune times during compilation/packing; * people using the Eclipse Java Compiler, a IDE compiler designed to be useful with bad Java; * people trusting themselves writting XML annotations instead of Java annotations, and not unit testing the code (this lack of unit tests alone probably means the code literally did not even work on their machine); * people using the existential, compile-on-runtime terror that is Java Server Pages.
jayd16 4y ago
>and letting the framework deal with the configuration You could even say that the frameworks put the config on rails. But seriously, just embed the server. Its not a bad deal at all.