And the winner is …

Currently there is almost no time to work on Babel-17. And unfortunately, it does not look like this is going to change in the near future. The good thing is that this makes the decision of what path to choose for the further development of Babel-17 easier. The interpreter part of Babel-17 will be written in Scala and actually be name- and stack-based, and not continuation-passing. This means that the reference implementation will lack features like tail calls, recursion that is bound only by the heap size, not the stack size, and quick variable lookup via deBruijn indexing. It also means that about 2300 lines of code that have already been written will not make it into Babel-17 v0.21.

The upside is that the reference implementation will be pretty simple to understand and maintain as the Babel-17 spec progresses. The hope is that with a good spec and a faithful, easy to understand reference implementation of the spec, it will become possible to find collaborators who want to code (in Babel-17, preferably) Babel-17 compilers that target platforms like C, Java, .NET, iOS and JavaScript.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: