Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide some historical context for the platform #565

Merged
merged 1 commit into from
Dec 2, 2016
Merged

Provide some historical context for the platform #565

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 8 additions & 0 deletions blog/_posts/2016-11-28-spp.md
View file
Open in desktop
Expand Up @@ -11,6 +11,14 @@ simple; let's reduce the Scala standard library to a very small core, and open
up the decision about what popular libraries should be shipped in a "batteries
included" distribution of Scala. This is the basic idea of the Scala Platform.

The Scala Platform is the logical continuation of the modularization effort
that began in Scala 2.11. Ultimately, the scala-library should be a small core,
that consists of the Scala types we've come to think of as part of the language,
such as the collections and most classes defined directly in the `scala` package.
The modularization of xml, swing and parser combinators has made it easier for
community maintainers to step up, and the SPP will continue opening up the
standard library to community involvement.

However, bringing many open source libraries together,
isn't easy, nor is is it easy to ensure that these essential libraries continue
to be developed. This is why we've come up with and proposed an initial draft of
Expand Down