Skip to content

Commit

Permalink
Removing reference to Python 3.
Browse files Browse the repository at this point in the history
  • Loading branch information
@mikeal
mikeal committed Feb 19, 2015
1 parent b67282f commit 5304e8d
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions ROADMAP.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,6 @@ When old versions of dependencies like V8 are no longer supported by their proje

## NG (Next Generation)

> This is not Python 3!

This comment has been minimized.

Sign in to view

Copy link
@domenic

domenic Feb 19, 2015

Contributor

It might be interesting to say something like "io.js has the benefit of learning from the past experience of many other platforms and languages, and will not repeat their mistakes by abandoning compatibility with existing code while building next-generation solutions. Instead, we plan to work on a system that allows next-generation evolutions of the core libraries to live alongside and interoperate with the existing versions." Then talk about ES2015 modules or versioned core modules you install from npm or similar.
In order for `io.js` to stay competitive we need to work on the next generation of the platform that can more accurately integrate and reflect the advancements in the language and the ecosystem.

While this constitutes a great leap forward for the platform we will be making this leap without breaking backwards compatibility with the existing ecosystem of modules.
Expand Down

0 comments on commit 5304e8d

Please sign in to comment.