Re: [scala-language] The cake’s problem, dotty des ign and the approach to modularity.

I agreed with all the range of discussion at the following HN thread. In 
particular, I want to call attention to the following post which emphasizes 
that Scala is not sufficiently simplified and unified. Scala 3 with the DOT 
(Dotty) proposal is attempting to make some headway, and my position is to 
try to remove subclassing (retain subtyping) and replace with a superior 
paradigm which is more unified, which will make the calculus more provable, 
will make type inference more simplifed and complete, and will remove the 
CAKE pattern and other warts which are giving Scala a bad rap while also 
slam dunking it to massive adoption...

https://news.ycombinator.com/item?id=9394108

This might be worth a read:
> http://codahale.com/the-rest-of-the-story/
> http://codahale.com/downloads/email-to-donald.txt
> Having worked with Scala; I'd say I love it.
> Having worked with Scala; I'd say don't use it for most projects.
> It is not the best language to start learning FP. Wrap your head around a 
> dedicated FP language and if you still feel the need for a hybrid FP/OO 
> language Scala is definitely worth a look.
> However as it is a hybrid I've felt it made my code just too complex. 
> Compared to Java there are a dozen more ways in Scala to fix something; and 
> often you struggle to find the best way. This takes a lot of learning and 
> it just isn't worth it. It's a great and elegant language in many ways, but 
> I've come to dislike a lot of features of it.
> Simplicity is one of those things that make a beautiful codebase. See also 
> (recently featured on HN)



-- 
You received this message because you are subscribed to the Google Groups "scala-language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.