3 ms·
Scala was the only time in the past decade I actually enjoyed programming, but it wasn’t a great idea to use for our relative large team as the amount of expres
by lightbendover 3y ago
Scala was the only time in the past decade I actually enjoyed programming, but it wasn’t a great idea to use for our relative large team as the amount of expression allowed comes at the expense of subjecting others to your mental model of how things should be done and having them spend undue time grokking it. I view this largely as a deficiency in style guidance, but Scala attracts very opinionated people in my experience and I say good luck to any style guide being upheld across a large org or team.
Kotlin has been nothing but great for me though. (Different company). It’s largely the best parts of Scala for me and without the headaches that come from some allowed patterns.
- VirusNewbie 3y ago>I view this largely as a deficiency in style guidance, but Scala attracts very opinionated people in my experience and I say good luck to any style guide being upheld across a large org or team. That's a great point, and probably one of the biggest downfalls of Scala. Not only did it allow for both 'java++' style programming, it also had full on almost 'haskell' style as well, and the community was split on which way was better! So yeah, any given codebase in the company could be a very tight, neat, compact monad transformer heavy functional program, or it could be a mess of untyped actors passing messages around to mutable state ridden monstrosities!
- mafribe 3y agoMulti-paradigm languages, and there are several popular ones including Scala, need strong software architecture enforcement. The software architects need to decide which style to use, e.g. purely functional and monadic, vs nicer-looking Java-style OO.
- c_crank 3y agoWhat a day to be alive, when Java-style OO is described as a nicer looking option!