- About Scala
- In the Enterprise
- Scala Community
- Language Research
- In the Press
- The Scala Team
- Scala's Prehistory
- Contact Us
- Learning Scala
- Tour of Scala
- Scala API
- Setup & Getting Started
- Programming Guides
- Other Guides
- Code Examples
- Scala Developers
martin's post on ycombinator
Was wondering if people had seen Martin's post  in response to
the "new" complexity blog post ?
I am sympathetic to Martin's point that the collections might not be
arbitrarily extensible (they certainly aren't in many other languages).
However, I'm not sure that taking away things like implicit conversion
will address many of the problems brought up later in the original post
(e.g. the sortBy failure) since this is code that doesn't look like
it's trying to do anything fancy. I don't think these are cases of a
developer cutting herself on a dangerous tool.
I'm also a bit nervous--if implicit parameters and enrichment become
frowned-upon (or "second-class") constructions in Scala then it will
have serious implications for things like the type class pattern (which
I am currently finding hugely useful).
What do you all think?