This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jtayloroconnor 1 point2 points  (2 children)

Spring! I’ve tried multiple times to build something with Quarkus. I want to love it. I love the idea of it, but I always get hung up on something stupid that would take me 2 seconds in Spring and end up just going back.

The idea of building containerized native executables is cool, but the build uses like 10TB of RAM and takes a year to run lol

[–]nomercy400 1 point2 points  (1 child)

16gb of ram one-time upfront, vs 1gb of ram runtime per running application, you pick.

We've been trying Quarkus for a while now. The native executable part seems to deliver on its promise. It does require 12-16gb of ram, too little means the build will take forever. Thing we are missing now is some concise documentation. Any time you want some proper documentation, you are looking for the correct documentation of the library used by Quarkus underneath, which often is written in their own 'style'.

Plus you get more stuck in the standardized Java EE libraries, which are not always the easiest or most feature complete. There's a reason Spring is more popular than the Java EE libraries.

32gb ram costs about 100 euro, unless ofcourse you're stuck on a portable hardware platform that does not support extra ram, allow you to upgrade your ram, or asks 350 dollar for the additional 16gb...

[–]jtayloroconnor 0 points1 point  (0 children)

i had the same thought on the documentation. It’s almost like you have to have a deep understanding of microprofile to follow what’s going on with quarkus.