Hacker News new | ask | show | jobs
by gadflyinyoureye 84 days ago
Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use? Spring itself is a wildly adopted standard. It is a semi open standard in that anyone can use it freely, but in that it's not supposed to be implemented by others.

The same is true for Micronaught or Quarkus. Learn the frameworks. But they are not a new open standard.
3 comments
henk53 84 days ago
> Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use?

People don't really talk about Jakarta EE as "the standard". Haven't been doing that for quite some time.

You learn it so you don't hand Spring the ultimate monopoly. I thought we all didn't like monopolies? Why give Broadcom one?

link
freedomben 83 days ago
Yes please, though this is largely driven by my personal dislike of Spring Boot. The bloat and magic sucks so much of the joy out of programming to me. That said, I never lived in Spring Boot exclusively. I've heard people say that it's an "all in" kind of thing and once you go all in and learn the thing really well, you start to like it.
link
bzzzt 84 days ago
There's nothing to be gained by picking a winner, especially if it doesn't really matter because the important APIs are the same.

Newer frameworks like Quarkus are specifically built for container usage and applications built with it are a bit faster and smaller than Spring boot.

link
gadflyinyoureye 83 days ago
I'm saying the spec lost to Spring. There are many historical reasons for the loss, but Spring won.

It looks like the industry is moving away from architectures like EE. The desire now is more like a Go deployment: single, self contained deployable. There are make frameworks that support this goal. Maybe EE is one of them, but it's not essential like it was in the early 2000s.

link
henk53 83 days ago
> single, self contained deployable

EE doesn't exclude that model at all.

For the most part, maybe like 99%, the Jakarta APIs are agnostic of what the deployment model is. They are APIs to validate input, service HTTP requests, store data in databases, look up roles, connect to identity providers, etc etc.

link
pjmlp 84 days ago
Except people keep forgetting they implement the standards on their very foundation.
link