- 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
Standard library or example implementations
Sat, 2011-06-18, 01:55
I just watched Martins keynote from Scala Exchange 2011 and it got me thinking.
There seems to be lots of plans to add various things to the standard
library. For example there was talk about adding a databse DSL. Is
this really a good idea?
I'm thinking that adding all this stuff to the standard library is risky.
* You risk promoting an implementation that is "premature" in that
later experiments by third parties proves to be better in some
respects. Which leads to all sorts of issues regarding support and
* By doing it in the standard library you spend resources on specific
sub-domains that could potentially be better spent on more generic
* The life cycle of the library is tied to the language. So new
releases of either has to be synced with the other.
* By having a standard implementation there might be less of an
incentive by third parties to explore the area.
* The standard library gets bigger. I don't know how much of a problem
this is but the very existence of project jigsaw suggests that it
So instead of expanding the standard library, how about doing these
kinds of things as prototypes, distributed separately as subprojects.
Example implementations that can be used before there are good third
party solutions. This implementation will also serve as the test for
more generic features that can be adopted by said third parties.