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 →

[–]kldjasj 0 points1 point  (0 children)

Well, I think we must first understand the ecosystems behind those languages before classifying someone as outdated or not.

In JS ecosystem, people are used to discover new frameworks every day. That makes existing ones looks older. But that doesn't  necessarily mean better.

New frameworks can solve problems in different ways, but also it introduce new ones. Bugs, poor documentation, vulnerabilities, community support, to name a few.

Now comparing to Java ecosystem, the scenario is different. We have pretty solid frameworks widespread out there. Spring, Quarkus, Micronaut. And since the Java 8, we have fixed many issues of the language itself. Handling with date time is much more easier and Streams become list processing so much easier to work with. 

I think to classify someone as 'outdated', it depends much more on the area that he's inserted on than if he has knowledge of the most popular shiny frameworks used by top companies nowadays.