Yammer moving back to Java from Scala(gist.github.com)
gist.github.com
Yammer moving back to Java from Scala
https://gist.github.com/1406238
3 comments
Wow. Simply wow.
I say this as someone who's coding experience is essentially all web stack, and wouldn't consider myself a computer scientist, but that was one of the best reads this year. Gives me so much insight in why choosing a popular platform cough LAMP cough can be a good idea even when it feels so broken.
I say this as someone who's coding experience is essentially all web stack, and wouldn't consider myself a computer scientist, but that was one of the best reads this year. Gives me so much insight in why choosing a popular platform cough LAMP cough can be a good idea even when it feels so broken.
The performance rules they had to adopt are just painful:
Don't ever use a for-loop.
Don't ever use scala.collection.mutable.
Don't ever use scala.collection.immutable.
Always use private[this].
Avoid closures.
Sounds like they ended up in a situation where they were almost writing Java in Scala already.
Don't ever use a for-loop.
Don't ever use scala.collection.mutable.
Don't ever use scala.collection.immutable.
Always use private[this].
Avoid closures.
Sounds like they ended up in a situation where they were almost writing Java in Scala already.
Although I don't write much Scala, I love developing in JRuby (and Ruby in general) and Clojure, but in a lot of situations Plain Old Java (POJ) really makes the most sense. The issues are speed of experimental programming in alternative JVM languages vs. overhead to lack of tooling and deployment issues.
I think that the future "most used language of the JVM" will likely not be Java but I don't know what that language will be (and it has maybe not been created yet).