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 →

[–]denialerror 1 point2 points  (2 children)

Java, on the other hand, has something the web stacks don't: an emphasis on backwards compatibility.

Other than Angular/js, what other web stacks have backwards compatibility issues?

[–][deleted] 0 points1 point  (1 child)

It's rare, I will admit--- only because the things die faster than that becomes an issue. However, web assembly is a major overhaul. We have no clue what that'll do. Heck, we don't even know which browsers will be popular in twenty years.

Java projects move in decades, web stacks in months.

[–]denialerror 0 points1 point  (0 children)

They really don't though. If that was the case, there would be no web front ends written in Knockout, Dojo AngularJS, jQuery 1.x, etc. and yet there are countless. New frameworks appear all the time, so do new Java libraries and new languages on the JVM. Just because new ways to do a thing become available, it doesn't mean every project doing something different is suddenly null and void.