2 ms·
I don’t think it is harder than any other ecosystem of similar size, it’s just unknown to you and feel different. Jakarta EE is the old Java EE’s continuation,
by kaba0 4y ago
I don’t think it is harder than any other ecosystem of similar size, it’s just unknown to you and feel different.
Jakarta EE is the old Java EE’s continuation, which is a huge standard for solving many kinds of complex business requirements (dependency injection mostly, with aspect-oriented programming). In a way it is a Spring alternative, but the truth is that Spring also uses several annotation of the standard so it more like building on top a subset of it. While it is a difficult topic, it is an ecosystem in its own right, so I don’t think it is meaningful to discuss it with Java itself — one can make a whole career as a java dev without touching it.
Package management is basically either maven or gradle, but both use the same registry for the most part, so on the surface level they both are quite easy to use.
I would guess you mean java’s versioning (eg. 8, 17, etc) - this couldn’t be easier, it’s just an integer that increases every 6 months. That is, for OpenJDK. This is the JVM-implementation, being both the reference and the most often used one. It has several forks that you might have heard of, but they share more than they differ. Some of these forks/vendors provide LTS-releases and this usually targets 8, 11, 17, 11+6k versions. That’s pretty much it.
In the meanwhile you literally have to use a tool to generate a base repo to write anything more complex than hello world in the JS ecosystem :D