News for hackers. Stuff that matters.
Re:Open-Sourcing Twitter Heron by pron on Wednesday May 25, 2016 @07:01PM (#11773860)
Aside from Erlang which is far too slow (most Erlang apps use C for the data plane) the others are far too risky choices in terms of hiring, future support and general maintainability. Also there are far too many unknowns about them. Rust shows a lot of promise and may very well be suitable for this kind of things, but it may still be too young for an important infrastructure project at Twitter. It is also harder to program than in Java, although for an infrastructure project such as this, this may not be a deal breaker.

Another reason to run on the JVM is that often your applications run on the JVM, and the JIT -- which is getting better and better, and will get incredibly good in Java 9 -- can really do cool stuff when it optimizes across the app/infrastructure line. I've just seen a paper[1] showing 3x performance boost when rewriting parts of SQLite in Python, and letting the JIT optimize the DB together with the app.

[1]: http://arxiv.org/abs/1512.03207

Re:Open-Sourcing Twitter Heron by technion on Friday May 27, 2016 @12:13AM (#11783865)

    Aside from Erlang which is far too slow (most Erlang apps use C for the data plane) 
I'm going to call "citation needed" on that. Riak and EJabberd have a reputation for scale and performance, and the only C I can see referenced is where existing libraries like Zlib get used.

Edit: You are still right. The hiring issues are relevant, and apply to Erlang also.

Re:Open-Sourcing Twitter Heron by hyperpape on Wednesday May 25, 2016 @08:49PM (#11774384)
Is there any kind of overview of the JIT improvements coming in Java 9, or do you have to follow the relevant mailing lists/commits?
Re:Open-Sourcing Twitter Heron by pron on Wednesday May 25, 2016 @09:26PM (#11774568)
I'm referring to Graal, which would be available in Java 9 as an alternative JIT to HotSpot's C2 compiler: https://wiki.openjdk.java.net/display/Graal/Publications+and...