Java is back? Programming language trends for 2345 teams(blog.helloworldopen.com)
blog.helloworldopen.com
Java is back? Programming language trends for 2345 teams
http://blog.helloworldopen.com/post/83402776977/java-is-back-programming-language-trends-in-hwo
7 comments
Java isn't back, it simply never went away - it's the modern Cobol. It's a good environment for backend development. Free if you need it, support if you want, no vendor lock-in, no platform lock-in, a vibrant open-source community - there's a lot to like about this old dinosaur!
Actually back in 2012 Java wasn't that popular. Here's the language stats for the 200 teams 1.5 years ago:
Ruby 28.4%
Python 27.5%
Clojure 10.1%
Java 9.2%
CoffeeScript 8.3%
Haskell 6.4%
JavaScript 5.5%
Scala 1.8%
Go 1.8%
Groovy 0.9%
Considering the difference in sample size and make-up, the latest results just show the competition is gaining broader appeal and with it more mainstream languages start to dominate.
This is surprising. Your article portrayed Haskell as having gained a fair amount of ground, but actually it seems that it dropped in half or so.
> describes haskell as having a "nice emphasis on functional programming"
understatement of the century
understatement of the century
Java is here to stay. We are a small startup, but I am building our entire backend in Java 8.
definitely a smart choice...especially if you are thinking of something that can adapt to evolving technology, so far I haven't found a platform quite as flexible.
Yup, following the herd is the best way to go. Especially if it means that everyone bigger than you can afford to hire the best and brightest at salaries you can't even dream of matching....
This is the language usage from latest Google Code Jam stats: http://www.go-hero.net/jam/14/round/0
Some observations: * C++ is the king. More people use it than next two (Java+Python combined)
* Although there were 20% more Java coders than Python coders, but 20% more Python coders qualified than Java coders.
Some observations: * C++ is the king. More people use it than next two (Java+Python combined)
* Although there were 20% more Java coders than Python coders, but 20% more Python coders qualified than Java coders.
JVM languages would probably top such lists in coming years.
Think JRuby, Jython, Clojure,Javascript...etc and of course Java.
For anyone interested in trying these out, checkout HiveMind (crudzilla.com), I am the developer.
Sample screencast: http://crudzilla.com/assets/img/info-graphics/lang-demo.gif
Think JRuby, Jython, Clojure,Javascript...etc and of course Java.
For anyone interested in trying these out, checkout HiveMind (crudzilla.com), I am the developer.
Sample screencast: http://crudzilla.com/assets/img/info-graphics/lang-demo.gif
What's the reason to use HiveMind over another solution?
HiveMind is for building web apps, as opposed to being just a generic IDE.
You can read the docs or just download and try it out...there are a lot of interesting ideas implemented on the platform.
You can read the docs or just download and try it out...there are a lot of interesting ideas implemented on the platform.
The name of this article is definitely leading without context. For a competition that is focused on building a race car simulator, certain languages are going to be a better choice. If the competition was to build a web app, I'm pretty sure that C/C++ would not be high on that list, and Java would be ranked lower.
Hi!
Unfortunately there's quite a bit of context behind those statistics that doesn't fit in to the title nicely.
I suspect that mentioning just HWO or Hello World Open or real time race car AI coding competition is not enough either. Do you have any suggestions on what would be a good title?
Unfortunately there's quite a bit of context behind those statistics that doesn't fit in to the title nicely.
I suspect that mentioning just HWO or Hello World Open or real time race car AI coding competition is not enough either. Do you have any suggestions on what would be a good title?
Thank you for the emphatic greetings. Normally, when I see articles with similar titles, they are articles about general programming trends. I realize that HN does not like link submissions article names to be modified. Since the article is on a website about a race car AI contest, the website does not need to provide context in the article. I'm just saying that if I was skimming through HN articles and saw the article title, I may get the impression that Java is the new old hot again.
Android...I'm still hoping Google will soon focus on Go and deprecate the usage of Java language for Android.
Why would they deprecate Java? Especially why would they replace it with a relatively immature language and implementation? I'm not knocking Go--it is simply a fact that the language is immature still, just like every language that is relatively new.
Is there a specific reason on why? Just curious?
The usual argument "You have to use the newest shiniest tech or you suck"
I'm not an Android programmer, but I hear that the Dalvik-based Java is Java 6ish, and will likely stay that way, while Java (from Oracle) moves forward. Much bad has been said about Java 6. So from that perspective, one might hope for a change.
Any reason why Go is better than Java on Android? Concurrency is the reason? I personally think Go is good for System Programming, e.g. Docker, GoRouter (Cloud Foundry), etc.
I have a personal preference for Go over Java, but I'd say Go's big focus on concurrency is a big win for mobile , where you don't need to compute many things but need to react to many exterior stimuli.
Should get faster binaries, thus better on the batteries. I think better compile times would help with the edit-compile-run cycle.
Another reason would be that JNI is horrible and if you need to mix your app with native code you are out of luck.
So Go solve the problem, right? How is Go's OpenGL/OpenGL ES?
Is the Go FFI any better? How does it interact with the garbage collector? What aspects of the JNI are horrible in your mind (I have a few in mind as well) and how does the Go FFI differ?
The most common solution in go is to use cgo[0] when wanting to bind with another language. From C you can then do whatever you'd like. That's how people are interacting with OpenGL[1] or QT[2] for example. Though, it seems like most common use cases of Go are to stay within the libraries supported by the shipping library or 3rd party libraries written in pure Go.
[0] http://golang.org/cmd/cgo/
[1] https://github.com/go-gl/gl
[2] https://code.google.com/p/goqt/
[0] http://golang.org/cmd/cgo/
[1] https://github.com/go-gl/gl
[2] https://code.google.com/p/goqt/
Right, but how is that different than JNI?
For instance one of the major complaints about the JNI is that adds a pretty high performance penalty to any native calls (and typically you want native calls when performance is important). Does Go's FFI not have this performance penalty? If not, why not?
Like with the JNI, Go's garbage collector needs to understand life cycle semantics of objects coming in/out of the native binding, how is this accomplished and does it do a good job? Does it complicate the garbage collection of other unrelated parts of the system?
Basically, if you are going to claim that the JNI is awful (and I think that is a valid claim) and then imply that Go's isn't, I'd like to know why that is.
For instance one of the major complaints about the JNI is that adds a pretty high performance penalty to any native calls (and typically you want native calls when performance is important). Does Go's FFI not have this performance penalty? If not, why not?
Like with the JNI, Go's garbage collector needs to understand life cycle semantics of objects coming in/out of the native binding, how is this accomplished and does it do a good job? Does it complicate the garbage collection of other unrelated parts of the system?
Basically, if you are going to claim that the JNI is awful (and I think that is a valid claim) and then imply that Go's isn't, I'd like to know why that is.
The go runtime will manage memory of thins allocated in Go land but you must manage memory in C land.
If you allocate memory using C.malloc you must use C.free otherwise you will leak memory.
If you allocate memory using C.malloc you must use C.free otherwise you will leak memory.
Which again is very similar to JNI. I'm genuinely curious as to how Go's FFI differs from Java's to make that a distinguishing characteristic between the 2 languages.
So how can native code get access to objects on the Go heap?