3 ms·
It's a fundamental misreading of the situation. Language geeks want language geeking, what Scala users want is a "faster horse". (Faster compiler, nicer projec
by pas 2y ago
It's a fundamental misreading of the situation.
Language geeks want language geeking, what Scala users want is a "faster horse". (Faster compiler, nicer project/package manager [sorry sbt], incremental compiler, LSP-compatible compiler, and so on. All good and nice and completely valid and important things!)
Unfortunately usually corporate backers can deliver these things not language researchers.
There's no need for the tooling and community to keep up. If Scala 2.12 is so good for the community stick with it.
The obvious problem is that Scala 3 delivers features (and whatever Odersky et al. cooks up will likely be useful for a lot of Scala users) that incentivizes attention fragmentation.
Yes, it's true that the community cannot keep up. (Yet the community is not a hivemind, it was able to churn out so many effect libs over the years I lost count.)
But it's an unforced error to put this responsibility on the researchers.
- ATMLOTTOBEER 2y agoThis is a fair characterization. Unfortunately Scala's corporate backing is weak compared to something like Java. So the people in the best position to give us a faster horse are in fact these researchers. :(
- pas 2y agoThat might be so, and it's okay to kindly tell them that, but to me it seems the community is pretty abusive regarding the researchers sometimes. (Well, and ... in general, Scala drama was not unheard of over the years, powerful languages tend to attract people with their powerful vision. And of course said researchers' people skills tend to show some room for improvement from time to time.) Anyway, squeezing water from stone might be easier than persuading certain folks :)