2 ms·
Some things that you could learn: * important concepts such as f-bounded polymorphism, covariance, contravariance, implicit parameters and methods, etc. * tr
by amichail 19y ago
Some things that you could learn:
* important concepts such as f-bounded polymorphism, covariance, contravariance, implicit parameters and methods, etc.
* traits that solve the diamond problem with multiple inheritance
* functional programming concepts including monads
* advanced concurrency concepts via the actors library
* pattern matching via case classes and extractors
* that type inference can make you highly productive in a statically typed language
- mooneater 19y agoI'm sure you have good reasons for what you said about Scala. But as someone who does not know Scala, the post is not motivating. Could you state the case for scala, in terms that someone not familiar with it, could appreciate?
- amichail 19y agoAre you familiar with most of these concepts already?
- anamax 19y ago> that type inference can make you highly productive in a statically typed language Oh really? Type declarations and the like are at most 10% of code. That means that eliminating the need to type them, which is what type inference does, can't decrease code size by more than 10%. It's unlikely that that 10% takes more than 10-15% of development time.
- runningskull 19y ago10-15% of software development time is a lot. A whole lot. I'm not commenting on whether type inference saves that much time, but if it does, it's undoubtedly worth it.
- anamax 19y agoWhile 10-15% was generous, 5% is "worth it". However, "worth it" isn't the relevant standard - the claim was "can make you highly productive". 10-15% isn't a "highly productive" difference.
- anamax 19y ago> * important concepts such as f-bounded polymorphism, covariance, contravariance, implicit parameters and methods, etc. The fact that those are important concepts in Scala doesn't make them important concepts. > traits that solve the diamond problem with multiple inheritance There are lots of solutions to the diamond problem. The fact that scala uses traits doesn't make traits important. > * pattern matching via case classes and extractors Again, so what? Scala is full of elegant mechanisms to solve problems that resulted from design choices. The elegance of those mechanisms or their importance to scala doesn't make them important. After all, one might reasonably have made different design decisions, making them irrelevant.
- amichail 19y agoMany people are not aware of the issues. This would be a learning experience for them that starts from a familiar base.
- anamax 19y agoNot so fast. The claim was that scala is special. However, the argument doesn't support that claim. It's a list of "me-toos" and hyperbole. For example, every language with multiple inheritance has some mechanism to deal with diamonds. Type inference is useful/interesting, but it doesn't result in "highly productive".