In a previous e-mail, I pointed out that among the many changes, the most obvious is that the development of using other popular languages on the JVM on the Java domain has become more and more rapid. Some old and new-created JVM-based languages---JRuby and Jython, Java-style languages---Groovy and Scala and brand, new languages---Clojure and Kotlin, These languages give us a choice------get the performance and reliability of the JVM but can use a different syntax.
In an ideal world, all developers can choose their own language. The reality is that, as a developer, we are constrained by what language is actually used by the company that is suitable for (our) language and support for the tool. First of all, the language you choose for your field---can make your job quick and easy, and more importantly for your non-functional needs such as: performance can be quickly and easily. Second, no one wants to be used as a simple editor to process the coding process-menial (yard farming). Yes, I know that we can all use vim and Emacs or popular Ides such as IntelliJ or eclipse to easily and quickly refactor large pieces of code (Hello tdd! )。 Thirdly, the reality is that in our position (the position) very little can guide (decide) What language our employer chooses. Learning an ever-rising language means you have more jobs in the future, but employers decide to choose the right language.
In fact, many companies boast that they use the latest language because it makes them more attractive to recruit others. You can't help but focus on Twitter and Twitter. "Our company has changed the development process by a new language." But is this a real scene?
There is a useful industry-recognized trend map on indeed.com that we can continue to work on. In the Tiobe grandfather's generation of language pictures, but in the following two points are not used. a) it does not provide enough information b) It is a simple game. - Yes, we know it's Delphi (yes,delphi Dudes). Now, before you complain, I know that it's a long way from perfect and scientific to use this kind of approach. But unless you want to do a longitudinal study, ask all the companies what they are using? Believe that their answer is true rather than a marketing gimmick, to show that it may be good enough to explain (the popular language)
Well, this tells us about how the industry looks at the JVM's main language: Java,groovy,scala,clojure,jython and JRuby *. What happens when we look at the percentage of all the languages involved in the job?
Well, well ... It is clear that in the industry despite the din of other languages, Java is still a large presence, with almost 3.5% of the jobs market demanding Java knowledge. As we all know, Java is an industry heavyweight, but a little surprised, compared to other languages is a difficult to distinguish the line. With a total of nearly 0 lines, they need a lot of exponential growth to start threatening Java.
What happens when you take away Java
It's a lot of fun. First, Jython is really accepting the first language on the JVM than other java. Groovy began to pick up 2007 and soon became the alternative language first, no doubt, and by Grails,clojure and JRuby never got too much support. Despite the rise in the last 18 months or so. I think the most interesting point is that the acceptance in Scala has recently increased. The current row of Jython back row third, the gradient indicates that it will soon enter second. By placing Scala and groovy on a relative benchmark to compare their growth rates, we'll see the following.
So we can see that Scala has finally surpassed groovy's growth rate. So we can say that when you want to brush up on the old groovy textbook you may have a look at Scala, but the best thing you can do is keep your Java level (in these languages) at the top level. Insiders are concerned about Java is the JVM language boss when the end? But it seems to be on the road (the way to be replaced).
Scala, Groovy, Clojure, Jython, JRuby and Java----our working languages