A thought on the SBTB 2015 Panel on Past, Present and Future of Scala
Simon Ochsenreither <simon.ochsenreither <at> gmail.com>
2015-10-04 22:27:17 GMT
During the debate, I think there was a great question/comment about Scala being not too "separable" in terms of learning concepts of the language: https://youtu.be/xUWNcL7NRxg?t=29m40s
I just want to add another thought to the question and the answers that followed:
Our strive to have a dense feature interaction matrix kind of clashes with the desire to have a language with easily separable pieces, so the problems are inherent in our approach. In my opinion the lesson is not to abandon this philosophy, but to make sure that explanations and documentation goes the extra mile, which might not be necessary in less coherent languages.
This could also explain a bit why people say "Scala is hard, ... but I can kind of deal with C#", despite C# being a great definition of a kitchen sink language: C# has so many features which can't be combined with each other that the individual bits and pieces feel more manageable, and question like "what happens when I combine A with B and leverage C in addition?" (answer: you can't, it's probably already falling apart at step B) never need to be considered.
What do yo think?
You received this message because you are subscribed to the Google Groups "scala-debate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-debate+unsubscribe <at> googlegroups.com
For more options, visit https://groups.google.com/d/optout