4 ms·

> that has no serious rival in breadth/depth/ease of use balance. What about Jakarta EE?

by henk53 4y ago

invalidname 4y ago
The entire standard including all the dozen vendors shipping products occupy about 10-20% of the market based on our stats. Spring dominates the market. It's been around longer than Jakarta and influenced it a lot. Since that's made of multiple implementations there are advantages and disadvantages involved. Don't get me wrong. I like Jakarta, Quarkus et al. They bring a lot to the table and the cross pollination with Spring (which goes both ways) is great. But if you want to hire someone the chance of them having real world experience with Spring is much bigger than them having similar experience with Jakarta EE. If they have Java EE experience it isn't as applicable.
- henk53 4y ago
  > It's been around longer than Jakarta Not really, Jakarta came from Java EE, which came from J2EE, which was released early 2000. Spring is from 2003 and started essentially as a framework for J2EE. > and influenced it a lot. It goes both ways. Spring for instance started calling code "configuration" and wanted us to put it in huge amounts of XML. Java EE started with using annotations for bean definition and injection. Spring was initially against this idea, arguing configuration should be external and not embedded in the code. Citing that you would otherwise needed to recompile your code in order to change configuration. Many years later Spring projects barely use those huge XML files anymore and its all autowire.
  - invalidname 4y ago
    Not really. J2EE has been around for a while. But it was RADICALLY different and was pretty much horrible. Then it copied many of the AOP aspects of Spring (inject etc) as it evolved. The current standard of Jakarta looks more like Spring than its original form. As such most of the implementations of the standard are much newer. So yes, the standard origins are old but that's not a relevant metric. I said, cross pollination. E.g. just recently the Spring Native example is totally an example of Spring copying a great idea from the Quarkus et al.

> that has no serious rival in breadth/depth/ease of use balance. What about Jakarta EE?

by henk53 4y ago

> that has no serious rival in breadth/depth/ease of use balance. What about Jakarta EE?

The entire standard including all the dozen vendors shipping products occupy about 10-20% of the market based on our stats. Spring dominates the market. It's been around longer than Jakarta and influenced it a lot. Since that's made of multiple implementations there are advantages and disadvantages involved. Don't get me wrong. I like Jakarta, Quarkus et al. They bring a lot to the table and the cross pollination with Spring (which goes both ways) is great. But if you want to hire someone the chance of them having real world experience with Spring is much bigger than them having similar experience with Jakarta EE. If they have Java EE experience it isn't as applicable.

henk53 4y ago
> It's been around longer than Jakarta Not really, Jakarta came from Java EE, which came from J2EE, which was released early 2000. Spring is from 2003 and started essentially as a framework for J2EE. > and influenced it a lot. It goes both ways. Spring for instance started calling code "configuration" and wanted us to put it in huge amounts of XML. Java EE started with using annotations for bean definition and injection. Spring was initially against this idea, arguing configuration should be external and not embedded in the code. Citing that you would otherwise needed to recompile your code in order to change configuration. Many years later Spring projects barely use those huge XML files anymore and its all autowire.
- invalidname 4y ago
  Not really. J2EE has been around for a while. But it was RADICALLY different and was pretty much horrible. Then it copied many of the AOP aspects of Spring (inject etc) as it evolved. The current standard of Jakarta looks more like Spring than its original form. As such most of the implementations of the standard are much newer. So yes, the standard origins are old but that's not a relevant metric. I said, cross pollination. E.g. just recently the Spring Native example is totally an example of Spring copying a great idea from the Quarkus et al.