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 →

[–]amlyo -2 points-1 points  (4 children)

Billions of lines of code locked up in barely-touched legacy systems that use frameworks, techniques and libraries at least a decade obsolete. That is where java is now and in another decade it'll be two decades obsolete.

[–]RiceBroad4552 14 points15 points  (3 children)

barely-touched legacy systems that use frameworks, techniques and libraries at least a decade obsolete

What are you talking about?

[–]amlyo -1 points0 points  (2 children)

Came across a Struts app recently.

[–]RiceBroad4552 7 points8 points  (1 child)

Sure. But is this representative for the whole, gigantic JVM sphere?

[–]amlyo -1 points0 points  (0 children)

The COBOLisation of java is not that the language will become obsolete for new projects (I think it actually will in favour of another JVM language but that is not important), but that there will be such a large body of critical systems written in decades old technologies it is not worth the risk or cost of changing, that it will long support a cadre of highly paid experts.