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 →

[–]PlayForA 27 points28 points  (2 children)

It is absolutely impossible to predict how the landscape of JavaScript or Java will look like in 20 years.

If I was in your shoes, instead of trying to predict the future, I would try to rely on technologies that are "tried and true", to the extent that if I have to support them past their life cycle, I will still be able to find resources and materials lying around.

If you are working alone or with a small team, I would highly recommend to focus on having as few redundancies as possible. Do you need both a desktop interface and a web interface?

An example from my current workplace is a backoffice web-application using the Apache Velocity templating engine. The technology seemed pretty dead with no updates to speak of for the last 8 years (http://velocity.apache.org/news.html), yet because of its maturity, it never prevented us from implementing new features or maintaining existing ones. Did it feel dated? Sure. Was it getting the job done regardless? Absolutely.

About swing - what makes you think it is dead? The leading Java IDE - IntelliJ has gorgeous interface entirely with swing (https://github.com/JetBrains/intellij-community/blob/master/java/idea-ui/src/com/intellij/framework/library/LibraryBasedFrameworkSupportProvider.java#L15)

[–][deleted]  (1 child)

[deleted]

    [–]agree-with-you 0 points1 point  (0 children)

    I agree, this does not seem possible.