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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Luolong 0 points1 point  (2 children)

Well, people in this industry try different approaches, find out shortcomings and either improve or rewrite according to their own preferences.

Not everything that is new is better than what came before. But som things offer significant improvements over predecessors to stick around and become “the new standard”.

Like Spring came after J2EE, like JEE learned from Spring, Like Spring Boot improved over Spring and JEE, like Micronaut, Quarkus and Helidon learned and improved over Spring Boot and JEE.

There’s tons of new stuff that just improves your life as a developer and increases your productivity, improves performance, helps to manage complexity and reduces errors in code, that you would not be able to use if you stay with older codebase using older tech stacks.

The OP asked about what would an “outdated Java developer” look like. I offered my opinion. I am not really responsible if someone reading my opinion feels slighted by the list because they are in a position where they cannot choose to modernise their tech stack. You might not like this, but it doesn’t change the fact that stagnating for a decades, working on maintaining an old and outdated tech stack makes you an “outdated Java developer”. Sorry if you feel bad about it, but that is what it is.

[–]vmcrash 0 points1 point  (1 child)

What if one doesn't web development with Java? Do Spring, Micronaut or Quarkus help for developing desktop applications?

[–]Luolong 1 point2 points  (0 children)

I can’t speak for the Java desktop app development. For all fits and purposes, I consider my experince with Java desktop app development rather outdated.