4 ms·
It's only a disadvantage if you work with people that try to use every feature for every job. Admittedly some people do this, but you'll get the same problem in
by flukus 10y ago
It's only a disadvantage if you work with people that try to use every feature for every job. Admittedly some people do this, but you'll get the same problem in many languages like c++, ruby and c# as well.
The features are great for people writing libraries, but general purpose code should usually only need a subset.
- karim 10y agoThe problem with gargantuan languages like Scala and C++ is not that some people will try to use every feature, but that everybody will use a slightly different subset. Most reasonable people will agree on using a subset of the language but few will agree on what goes into that subset :)
- flukus 10y ago> Most reasonable people will agree on using a subset of the language but few will agree on what goes into that subset :) Why is that a problem? Different people/teams will have different needs. If I'm working on a problem where generics is a good fit and bob across the office is working on more business code where it isn't a good fit then it makes sense that we would both be using a different subset of the language.
- tatterdemalion 10y agoI need to understand all of the features to understand both your code and Bob's, especially when they interact. The point of "using a subset of a language" is having less feature interactions to understand.
- dman 10y agoFlip side is languages with such a small intellectual footprint that the moment that the problem domain / workloads shift a bit you are forced to switch to a different language.
- deleted 10y ago[deleted]
- timv 10y agoI hear that argument a lot, but it only seems to be true if you never need to look at code from outside your immediate team/project (either because you don't use it, or you use it without ever understanding it) In the case of Scala: If you ever browse the standard collections library you'll run into a lot of different variance rules and implicit constraints. It is quite hard to really understand the collections library if you don't get your head around those. If you want to use Spray for anything more complex than they spell out in their examples, then you need to understand their magnet pattern. If you want to be able to debug a problem in Slick then you'll need to understand shapeless. If you ever go anywhere near scalaz then you'll need to understand every esoteric symbol and operator in Scala, as well as be able to read and understand Haskell (because the patterns and types in Scalaz are often explained by reference to the Haskell equivalent) Yes, I can set rules for my own team about what features we use internally, but I want my team to at least broadly understand the syntax and patterns used in the APIs that they interface with, which means you need to either read & understand most of the features that you aren't using internally, or avoid a very large percentage of the scala ecosystem.