upvote
My experience with the defaults in JavaScript is that they’re pretty slow. It’s really, really easy to hit the limits of an express app and for those limits to be in your app code. I’ve worked on JVM backed apps and they’re memory hungry (well, they require a reallocation for the JVM) and they’re slow to boot but once they’re going they are absolutely ripping fast and your far more likely to be bottlenecked by your DB long before you need to start doing any horizontal scaling.
reply
Compile it to native (GraalVM) and you can get it fast while consuming less memory. But now your build is slow :)
reply
The minute a project has maven in it the build is slow. Don’t even get me started on Gradle…
reply
Fair point on ecosystem decisions, that's basically the thesis of the post. These patterns aren't Java being slow, they're developers (myself included) writing code that looks fine but works against the JVM. Enterprise Java gets a bad rap partly because these patterns compound silently across large codebases and nobody profiles until something breaks.
reply
Well, JS is fast and Go is faster, but Java is C++-fast.
reply
"Enterprise Java"

Factories! Factories everywhere!

reply
Yes! Obligatory link to the seminal work on the subject:

https://gwern.net/doc/cs/2005-09-30-smith-whyihateframeworks...

reply
Why do you think this plays out over and over again? What's the causal mechanisms of this strange attractor
reply