5 ms·
This is more of a split between techniques for programming-in-the-small vs. programming-in-the-large. All languages have this. You could write more or less the
by premium-concern 10y ago
This is more of a split between techniques for programming-in-the-small vs. programming-in-the-large.
All languages have this. You could write more or less the same list for Swift or Java with minimal changes.
Again, do you have any actual experience with this, or is this just your assumption? Because I have never seen this issue in the wild.
- timv 10y agoI have absolutely seen it in the wild, but at least in my case it seemed to be more a case of "People who wish they were writing Haskell, but found more commercial opportunities with Scala" compared with "People who found Scala to be an improvement over Java". At the extreme of the first group you'd have people for whom it seemed like every problem was best solved with a higher-kinded-type. And while it might well have been technically (and mathematically) elegant, the rest of the team was left scratching their heads trying to understand it.