4 ms·
The problem with scala is that the docs were too late to come. Those who put them out are geniuses (props Cats ppl, ZIO too) - but it seems it is now too late.
by idclip 7y ago
The problem with scala is that the docs were too late to come.
Those who put them out are geniuses (props Cats ppl, ZIO too) - but it seems it is now too late. You know there’s irony that alot of the earlier docs were based on haskell books, too.
Its not the math. Look at haskell’s freenode presense vs scala’s. Scala’s a 6th of haskell. What haskell had over scala is docs and community.
Scala was just too late, and my coworkers are all whispering Kotlin. It’s a real shame.
Irony edit: i actually maintain a scala codebase at work, one of two under thirty other devs who do, and me and one of the major players in the team were talking about this only two days ago. Sort of a sad kind of funny.
- stewbrew 7y agoThe problem with scala is that academic goals sometimes don't align too well with "industry needs".
- hocuspocus 7y agoThat's a complete myth, really. The Scala ecosystem has its fair share of problems, but Odersky and his lab's involvement and stewardship have never been one of them.
- stewbrew 7y agoJust an example: Why wasn't it a priority to make scala run well on dalvik? The place is taken by kotlin and is one of its strongest selling points.
- hocuspocus 7y agoBecause there never was a real demand for it? What does that have to do with Scala's academic roots? And what makes you think Scala needs Android to be successful? Android is completely irrelevant to most Java developers.
- oxnrtr 7y agoCore team didn't care about Android. Simple as that. :-)
- stewbrew 7y agoThat was pretty much my point.