3 ms·
>My latest example of this was learning Scala 5 years ago. Bet on something new, and then you get calls from all over the country to work on it, as most people
by bonobo3000 11y ago
>My latest example of this was learning Scala 5 years ago. Bet on something new, and then you get calls from all over the country to work on it, as most people are trying it, but few know what they are actually doing.
As a young dev, I really want to learn how to do this. I'm a newcomer to the Scala party, but I can definitely see it becoming a huge player and there are so many reasons - Odersky has basically a team of PhDs at EPFL constantly making awesome stuff for the language and they have made some incredible stuff - TASTY + scala-meta is one of the latest, Scala.JS is another, and really the list goes on and on.
But I'm only beginning to clue in on this now. Would've been great if I had jumped in earlier. If you don't mind me asking, how do you learn to pick the right horse? What were the signals for Scala? my guess now is the fact that Odersky was a major contributor to Java and built both a strong technical team and corporate backing, but thats hindsight ofcourse :)
- lgieron 11y agoI've picked up Scala four years ago. To see which technology is likely to rise, you need to think like big businesses do - in this case, Scala can be seen as a Java++(++++), whereas competing technologies, such as Clojure or Haskel, are a complete paradigm shift. Knowing that large businesses are risk averse, it was likely for Scala to win out. (although IMO the jury is still out on this, the adoption rate is not great and a lot of people who tried Scala got burned by it - it may very well be a forgotten language in 5-10 years).