Future Of Java !!!

General Tech Technology & Software 2 years ago

0 3 0 0 0 tuteeHUB earn credit +10 pts

5 Star Rating 1 Rating

Posted on 16 Aug 2022, this text provides information on Technology & Software related to General Tech. Please note that while accuracy is prioritized, the data presented might not be entirely correct or up-to-date. This information is offered for general knowledge and informational purposes only, and should not be considered as a substitute for professional advice.

Take Quiz To Earn Credits!

Turn Your Knowledge into Earnings.

tuteehub_quiz

Answers (3)

Post Answer
profilepic.png
manpreet Tuteehub forum best answer Best Answer 2 years ago

I was wondering, how long java is going to survive in front of kotlin.

profilepic.png
manpreet 2 years ago
  • It is still very well used and we’re beginning to see new stacks coming on the frontend like Node but leaving Java to handle the intense business applications. Java’s not going anywhere soon.
  • AR and VR are it for the next 10 years. It’s hard to see past Moore’s Law. We haven’t begun to tap into the possibilities of VR. It will open our minds more giving us the ability to see things we never thought possible.
  • It will come from unexpected places. Microservices and lightweight containers.Modularizing Java. Java has a great card to play making Java and JavaScript more collaborative, dynamic, and adaptive.
  • It’s very mature and will remain the language of choice for at least the next five years. It’s less about supporting the language for the backend ecosystems. The most revolutionary changes are the amount of data we’re putting through the APIs. We can do more than ever before. Java-based back ends can handle the data and scale. The object-oriented Java skillset helps. Java will always be the backend platform.
  • It will stick around with the legacy apps being written. It is the software language for enterprises because they can save time, money and resources. Few greenfield projects will be developed in Java outside the enterprise. Java will be where Cobol is today in 10 to 20 years.
  • Solid. Central place for statically compiled language. Improves productivity versus C++. Reduces errors at compilation time. JREs available for many platforms.
  • Slow loss of relevance over time, until it is ultimately seen as a specialized skill needed only by a few, similar to the way that mainframe languages are currently seen. As more and more infrastructure moves to the cloud or to cloud-like provisioning within an enterprise, pre-defined services, such as REST access to a simple database (e.g. Firebase), are dramatically less expensive and simpler to work with than services that allow hosting of arbitrary code (AWS, Google App Engine). Developers are rightly taking advantage of these low-cost, simple services whenever they can. This means there will be fewer developers using Java in the areas where Java has core strengths. For now, Java is being used in areas where it is relatively weak (e.g. UI construction in Android and in GWT, and service orchestration) simply because it has such an enormous ecosystem. The long-term trajectory of Java will be phased out in favor of more appropriate languages and tools. This will take a long time, and happen in bursts. The current resurgence of interest in JavaScript as a language for web UI is one such burst.
  • With other languages like Node JS and Python rising in popularity, the future of Java seems to lay with Android as it is still the primary language for Android development. Java used to be a popular introductory language at schools but has been recently bumped out by Python.
  • Big data. All languages are heading toward running just the code and function you need. Docker provides an abstraction to run containers on top. The last layer becoming popular is server less architecture. Amazon Lambda only runs certain functions when an action takes place. You simply solve the problem by writing code and sharing it with a small team of Amazon engineers who will run it for you.
  • It’s very bright given the community and ecosystem. Significant corporate sponsors and the quality of the community add too much value and quality technology for it to diminish. Given that Java continues to have proper governance and community, I see it having a long life.
  • It will remain viable because it’s a huge asset in many enterprises – including ours. While there’s a lot of new technology available, it’s easy to find people who know Java. The main risk is microservices. The language can be different for each microservice. This wasn’t much of an issue two years ago but I can see it moving us from 99% Java, to 90% to 70% to 50% over time. We’re using more JavaScript and Node JS and some Go with Docker.
  • After being in decline for a while we see it trending up with the adoption of Java 8 by the enterprise. It will remain the predominant language in coding for quite a while. It’s the number one language that companies choose.
  • It’ll be around for the next 10 to 15 years. It’s easy to learn and is evolving to be more developer friendly.

0 views   0 shares

profilepic.png
manpreet 2 years ago

 

The future of Java continues to be strong in the near-term.

Java will be around for a good long time, it’s basically become this generation’s COBOL.

Java developers, on the other hand, have a more nuanced future.

The Java language is slowly incorporating bits and pieces of syntax from newer languages. This seems to be staving off irrelevance, but it’ll fail eventually - I’m fairly certain the JVM will outlive Java.

A Java developer who’s content using the parts of Java with which they are currently comfortable will stagnate themself out of the job market - could you imagine hiring a developer who refuses to use Generics?

A Java developer who keeps themself up to date with the evolution of the Java language will have plenty of job opportunities and codebases to maintain for decades to come.

A Java developer who enthusiastically incorporates these new language features will eventually be seduced away from Java by the sweet syntax of newer languages (can you hear the whispers? Scala … Kotlin … Closure … Haskel …). They may stay on the JVM, and may occasionally work in Java when the situation calls for it, but they won’t think of themself as a “Java developer” - they’ll be a developer who happens to use Java at the moment


0 views   0 shares

No matter what stage you're at in your education or career, TuteeHub will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.