3 ms·
And you still haven't explained how Scala has a similar problem.
by frowaway001 12y ago
And you still haven't explained how Scala has a similar problem.
- pjmlp 12y agoI am not the OP. Just commenting on this > Scala has been throwing out bad features in pretty much every single release for the last 5 years. You cannot throw out features in a language with the community size C# has, otherwise you just get another Python 3.0.
- frowaway001 12y agoI'm not sure comparing C# to Python makes sense. a) Microsoft is in an excellent position to make such changes, unlike Python, because Microsoft shops will largely do whatever Microsoft tells them. Just have a look at how often they have incompatibly changed the standard library used by C#. b) Not every language has to botch the transition as badly as Python designers did.
- Vektorweg 12y agoScala keeps features for imperative and functional programming, which is one category too many, because they solve the same problem just different. Thats how Scala is supposed to work. Its impossible to remove an approach.
- frowaway001 12y agoThat's not even remotely related to the topic, isn't it?
- Vektorweg 12y agoTheoretically, everything is related to each other. Practically, no.