Java is back? Programming language trends for 2345 teams(blog.helloworldopen.com) |
Java is back? Programming language trends for 2345 teams(blog.helloworldopen.com) |
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%
understatement of the century
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.
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
You can read the docs or just download and try it out...there are a lot of interesting ideas implemented on the platform.
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?
[0] http://golang.org/cmd/cgo/
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.
If you allocate memory using C.malloc you must use C.free otherwise you will leak memory.
