Did an intro to functional programming course in Scala.

Felt like I was able to touch the face of an immutable God. :')

Why does nobody use scala or require it in jobs anymore?

@b2plane I wanted to see purity and immutability in action.

We have some of our core services written in Scala (not the ones I work on). Additionally, Java has been marching into becoming more functional. (And java as you know, is quite pervasive)

Probably would have done the course in Haskell if it were offered.

@b2plane Because of business reasons more than technical. Scala devs are hard to recruit for, expensive, hard to keep. And with general purpose languages like Kotlin and even Java embracing *some* functional elements, it's rare that a problem is functional enough to offset the business hassle of a niche language.

Agreed. The learning curve was a bit much, as someone who's predominantly done procedural and OOP.

Simple functional constructs were taking too much time to write in Scala, but boy was it easy to read it.

You don‘t need to go full functional to get the benefits of immutability.
Languages like Rust or Swift have immutability by default and special syntax to make stuff mutable.

@Lensflare boom headshoot, scala is not entirely and purely functional tho, it can work through gradual steps. My issue with Scala is that it can bring in lots of clever code. I don't like people being clever with code, I want them being explicit

@b2plane errr. Scala is still the main popular language to do Spark stuff in afaik.

I've written a few ETL jobs in Scala, quite proud of those because they took me an age to figure out 🙈