My affair with Scala started in 2009, right in between Scala 2.7 and 2.8. I’ve been using Java EE for more than 10 years to build banking software, but this time I was looking to build lighter software to support my master’s studies in civil engineering. The idea was to lift ordinary calculations into expressions, not only to get some values back but also to document the entire computation flow. Only Scala could do it with implicit conversions, operator overloading, DSL-style support, and super-easy collection operations. Later, I fully embarked on the functional programming quest and began looking for all-Scala projects. After 17 years, I feel I’m still learning Scala :-)))
3 Likes
May be the best answer to this question has been given by Martin Odersky in Evolving Scala
Scala is safe and convenient at the same time.
Scala gives convenience of a dynamic language and more safety than other static languages. And it gives it without loosing runtime performance.
2 Likes
Thanks for the link, which I’d watched before but probably while coding.
As a reminder, my mother wasn’t paid either, but did it anyway.
I don’t advocate exploitative labor practices, but nor can we wait for industry to catch up.
We have to do it anyway. YOLO.
Edit: unrelatedly, I was reading old emails and saw that I mentioned to someone, also apropos of nothing:
I finally started following twitter feeds because of “ScalaDays” in NY last week.
Back in 2019 I was struggling with the types in a personal Java project of mine. Figured I needed some type-level computations for my abstractions to work, so I decided to learn Scala.