throwaway03452

4 ms·

1.
by throwaway03452 2y ago
I can only speak for myself, but I was lucky to be exposed to Spring Boot back in the v1.5 days after spending a few years creating Java programs without any framework. No XML at all, configuration by code, and opinionated default configura
2.
by throwaway03452 2y ago
Historically an upgrade could cause issues if the code or dependencies used undocumented functionality (like Byte code manipulation) or calls to native code, or the transitions to modules in v9. Upgrades after version 11 should be less &quo
3.
by throwaway03452 2y ago
If I ever found a startup I will mandate that we use Spring Boot (java/kotlin) until we grow big enough to afford the extra overhead with other frameworks. Spring Boot is truly a Get Stuff Done framework It would be hard to convince so
4.
by throwaway03452 2y ago
> The JVM is a massive memory sink Java tends to prefer using available memory, before it has to clean it. This results in memory usage growing more than it actually needs. Services often run in containers, so this is less than a problem
5.
by throwaway03452 2y ago
I don't share your experience. I have no problems importing a Maven project git clone https://github.com/... cd somedir mvn spring-boot:run
6.
by throwaway03452 2y ago
> you will never see `IntStream` kind of workarounds in C#. You may not see that in Java in the future either. Java will have value objects from the Valhalla project, and part of the plan is to replace Integer with a value object. Then
7.
by throwaway03452 2y ago
I choose Spring Boot anytime I have to create a service, just for that reason. The eco system is a huge force multiplier, and is constantly evolving. Spring Boot simplifies that a lot by simplifying the setup to the point where you often on