3 ms·
Have these two follow-up posts changed anyone's mind about the first? Yammer's productivity gains from Scala were apparently not greater than the losses due to
by socratic 15y ago
Have these two follow-up posts changed anyone's mind about the first?
Yammer's productivity gains from Scala were apparently not greater than the losses due to poor tooling and the impedance mismatch between Java/JVM and Scala. Therefore, the engineers all thought it was better to just go back to Java.
That seems like a useful data point, but certainly others' experiences might vary. Have these other posts added any extra information?
- brown9-2 15y agoI don't think they were intended to really change anyone's perspectives, but rather just clarify a private conversation accidentally made public. If anything, I just find it really odd that a company feels the need to have an official statement on what programming language they use/will use/might use.
- eropple 15y agoSame. I really, really like Scala, but I found it kind of strange that they felt obligated to go "wait wait wait, we like Scala, really...!"
- csmt 15y agoI think Coda did a good job in posting Yammer's official position clarifying the situation and it's a captivating blog post. Many people (including some people on HN) started criticizing Yammer because they decided to go back to Java. This blog post was in some sense necessary for Yammer.
- VonLipwig 15y agoIt was him trying to end all of the stories floating around caused by the private but public email. He didn't want the last word to be Yammer hates Scala and need's to jump ship. He thought it necessary to give a more balanced overview and provide subtext to the original message. I think he succeeded in doing this.