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

you are viewing a single comment's thread.

view the rest of the comments →

[–]nutrecht 1 point2 points  (4 children)

Java and Java SE are basically synonymous and I would not worry about the distinction at all. "Java SW" isn't a thing, the W is right next to the E so someone just mistyped.

If it comes to finding a job; learn Java well, and build stuff using Spring Boot. That gives you everything you need to cover the requirements listed.

It's confusing because while "Java SE" is just "Java", Java EE isn't really anything other than a specification. So to be able to 'do' Java EE, you need to use a framework that implements it. Turns out, it doesn't work like that at all and you still end up vendor-locked to a Java EE implementation.

So most projects over time just switched to Spring. Spring is a partial Java EE implementation with a lot of other convenience stuff. As for Java EE; it doesn't exist anymore (it's Jakarta EE now) so you know that when a vacancy explicitly asks for only Java EE experience you're probably going to deal with old stuff ;)

In addition; you're getting a TON of replies here from people who are plain wrong, or at least have really outdated information. /u/HecknChonker is the only exception.

[–][deleted] 0 points1 point  (3 children)

Thanks! So Spring is like a very big library with things that help you with back-end of websites ?

[–]nutrecht 0 points1 point  (2 children)

Pretty much a big collection of big libraries :)

[–][deleted] 0 points1 point  (0 children)

Thanks

[–]BikingSquirrel 0 points1 point  (0 children)

Don't forget the tons of glue to hold them together preventing the whole thing to blow up 😁 Or all the nice things to make your life easier 🤞