4 ms·
that's due to decreasing demand in java.
by sungju1203 8y ago
that's due to decreasing demand in java.
- twodave 8y agoI’m not sure that decreasing demand in Java is what led to a Jetbrains Java IDE overtaking Eclipse. The total pie may be smaller, which in itself is probably debatable and I’m not going to bother researching, but I believe the takeover has more to do with an active android programming ecosystem than any of the other factors mentioned in the article. It would be interesting to see a breakdown between IntelliJ editions with Android Studio broken into its own product line.
- stupidcar 8y ago[citation needed]
- fs111 8y agoDo you have any evidence to back that statement up? Java seems to be as popular as ever.
- austincheney 8y agoDoes it matter if they don't? People are entitled to opinions which may seem absurd. https://github.com/prettydiff/wisdom/blob/master/Avoiding_Trolls.md#citation-baiting https://github.com/prettydiff/wisdom/blob/master/Avoiding_Tr...
- vivaan 8y agoWhile it may be hard to show that Java's demand has decreased - and overall it may well not have since many companies which were using Java will continue to do so just by inertia - but for the latest generation of programmers, specially ones focused on ML / Data Science, Java feels like ancient history
- Elrac 8y agoYep. As a professional developer, I'm way over being excited and enthusiastic about Java; on some days, and having sampled more modern languages, I downright hate it. My guess is that the grandparent poster is mistaking this disillusionment for a decrease in demand. Like COBOL, I believe Java will continue to be the bread and butter of application programmers long after crossing popularity curves with a dead slug.
- foobarian 8y agoWhat's a good replacement for Java that has static typing and tool support? Is there one yet?
- Elrac 8y agoOn the JVM, the most solid contender is Scala. It's "better" than Java in a number of ways. Personally, I'm a bit turned off by the very intrusive role of the type system. You may find a bit less tool support than for Java (no surprise) and some of the clever functional-style code you write may run slower than less elegant corresponding Java code. Still, there are a lot of adapters, some big names, and they get stuff done. Scala being "harder" also allegedly attracts smarter developers. Another statically typed language, non-JVM, with decent momentum is Go. It's like C with a slew of sorely needed improvements. Very straightforward and there's often a single, obvious way to get something done. As a result I find I'm very productive in it. Performance is topnotch too. Tooling is quite good. I'm not sure it replaces Java as an "Enterprise" language for large-team projects though. Kotlin is another "better Java" language on the JVM. Pleasant enough to work with, but not as large an adopting community. Tooling is good if you like IntelliJ. C# is Microsoft's challenge to Java. Has borrowed some good ideas from Java and extended them, interfaces well with Windows (obviously). Tooling is good if you like Visual everything and Microsoft. Now may be a good time to switch to a language that more fully embraces functional programming. F# and OCaml are possibilities, Erlang has a great rep for stability, and Haskell is said to be very powerful but with a daunting learning curve. I'm experimenting with all of these and have the damndest time making up my mind. There's kind of an embarrassment of choice.
- naikrovek 8y agoA large number of Android developers would disagree with that statement.
- Bizarro 8y agoI'm guessing the vast majority of Android development is still using Java as its language, but I would assume with Kotlin being an official language for Android, that will be changing in the next few years. And of course, you're not really targetting the JVM when you're programming Android, but Dalvik or whatever runtime powers Android these days.