Over a million developers have joined DZone.

What Developers Need to Know About Java

DZone 's Guide to

What Developers Need to Know About Java

Let's examine the reasons why you might be considering a new language.

· Java Zone ·
Free Resource

To understand the current and future state of the Java Ecosystem, we reached out to our community for their insights. Unlike other topics like containers and security, there are far fewer people willing to share their thoughts on the current and future state of Java. This appears to be a function of its maturity relative to other technologies.

We are grateful to our three contributors who all have significant experience with Java:

We asked them, "What do developers need to keep in mind when working with Java?" Here's what they told us:

  • Java, today, is not the same as Java five or 15 years ago. New languages come along quite often. C++ was popular when Java came out. It’s really important to know why you are moving to new languages. Because they are new and sexier is not a good reason. Look at the stability of Java over the long term and the breadth and depth of the ecosystem. Remember to consider the enterprise software you will need: tools, CI/CD, test suites, class libraries, a suite of additional capabilities implemented in the new language. It will take years for any new language to achieve the richness of Java.
  • If you’re an established Java person, keep up the good fight. Make the case for adopting the new functionality and adopting the new platforms where it makes sense. If you’re new to Java, and Java is not something you’ve lived with, then you have a much larger menu to choose from with regards to the tools you adopt. Java in the enterprise is not going anywhere because of the existing code that’s in place. It works, it scales, people know how to run it and operate it. What you get out the JRE is the instrumentation and analysis and operational insights during runtime. Low overhead performance, tuning, and insights. You don’t get that from Perl, Python, C, and C++. The ability to get introspection while running is very interesting in the application world where we want things to run as long as we need them to. It’s an order of magnitude more manageable in production than any of the other runtimes out there that I am familiar with. It’s still a force to be reckoned with.
  • Java is meant to be a blue collar language for developers who need to solve actual problems. The thing developers should keep in mind is the problem they’re working to solve. One of the reasons behind Java’s success is removing previous distractors: memory management, certain aspects of security, and so on. The nicest thing about modern Java, especially the lambda syntax and Streams API, is that, when reading code, you can see the problem being solved.
java ecosystem ,Java ,ci/cd ,syntax ,Java 8 ,Streams ,Streams API ,code

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}