3 ms·
As a Scala user, every other language out there is still a painful step back. Kotlin or Typescript or even Rust are painful once you're used to having HKT and r
by lmm 4y ago
As a Scala user, every other language out there is still a painful step back. Kotlin or Typescript or even Rust are painful once you're used to having HKT and real monads. And while Haskell-the-language is good, if you think Scala tooling is bad....
I predict Scala will see an upswing for the same reason that OCaml has been on an upward trend in recent years; even if a language is no longer unhyped, if it's well-designed then it still ends up being the best way to get things done.
(The XML thing is a ten-years-out-of-date talking point, FTR)
- cutler 4y agoI predict the opposite and for the very reason you inadvertently suggested. The more Scala devotees obsess about HKT and dream of Haskell in their sleep the less relevant to business Scala will remain.
- lmm 4y agoHKT is the means, solving cross-cutting business concerns without fragile hacks (like reflection or metaclasses) is the end. If you use a language without HKT, you will have those flaky hacks in your codebase (because the alternatives are worse), you will have outages because of them, and your business will suffer (admittedly maybe not by enough to matter, depending what business you're in). Think back on your last outage - it's a good bet that using Scala would've prevented it.
- cutler 4y agoIf that was the case dynamic languages would be non-starters. Believe it or not there are a lot of businesses, some quite large, which have been chugging along quite nicely on PHP or Ruby for over a decade. HKTs may be fun to play with but let's get them in perspective as nice-to-haves.
- lmm 4y ago> Believe it or not there are a lot of businesses, some quite large, which have been chugging along quite nicely on PHP or Ruby for over a decade. Sure, and they either follow extraordinary development practices, or they have outages basically all the time (e.g. the famous Twitter "fail whale"). Like I said, in some lines of work (probably far more than people on HN would like to think, frankly) you can get away with that.
- Kwpolska 4y agoThe XML thing is still supported by the language, even if you need to install a separate first-party package to make use of it, so it is not an out-of-date talking point. There are other issues, such as the undebuggable macro system that has too much power, the insanely overloaded `implicit` keyword (fixed in Scala 3), or the two competing syntaxes introduced by Scala 3.