I don't think of promises as being particularly close to continuations, not even one-shot continuations. I think it's more "If you use promises you have to manually turn your code into continuations." :)
I wrote about my thoughts on that idea here: http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y...
One thing that has changed in the past few years is I don't see people comparing JS to Scheme very much anymore. I don't know if it's because JS got big enough with ES6 that the comparison seems forced, or because Scheme doesn't have the cachet it had a few years ago, or what.
Today, people who like JS seem to like it because they like JS — which usually means they like some combination of dynamic typing, JS's syntax, the platforms where JS runs, and the frameworks people built for it. I think those are all great reasons to prefer JS, much better than comparing it to some other language that it may or may not be similar to.
(There are also a lot of people who like JS today because it's the only language they know. I don't think that's a super informed choice, but everyone goes through a first love in their life, and the object of that affection doesn't say much more about its subject than the moment in time that they happened to start programming. My first love was Apple BASIC, but I think I turned out OK.)
In this respect JS is better. BASIC had the unique talent that although it was constrained like a "scripting" language, it didn't have the easy-to use high-level constructs. JS also was very minimal to start out with, but (a) you got something in return (the ability to run in a browser), and it was powerful in a few interesting ways (closures, and for good or ill, dynamic typing).
FutureBASIC was my jam. QuickBASIC was too slow so I tried to learn C, but it was brutal trying to learn that on my own. This was before the web and I knew zero people who knew any C. Something like a misplaced semicolon would get me stuck for weeks.
But FutureBASIC was almost as easy as QuickBASIC, fast enough for games, gave full access to the Macintosh Toolbox (graphics), and had a really cool visual interface builder (PG PRO). I could make software in it that looked like "real" Mac applications (which felt amazingly legitimizing to teenage me) and ran fast enough for real games.
It was really hard to make the switch to C because FutureBASIC was good enough for quite a long time. I wouldn't be where I am today without all the fun I had using it back then.
(but oh gods 'let' makes me so happy, having to get sensible closure behaviour by typing out let-over-lambda shenanigans by hand was -ing horrible)
Furthermore, there is already a compiler that implements first class delimited continuations in JavaScript: http://stopify.org
The project implements the control operator (which can implement other operators like call/cc). The research paper linked on the website talks about how control is implemented.
That's fair, agreed, and I don't mean to imply equality. The argument was that JS doesn't have continuations at all though, which wasn't completely true in 2013, and is trending less true over time with promises and generators, right?
Some might argue that a function which is so long that it needs block scoping, whether for visibility or storage lifetime management, is too long.
I guess it’s at least “mostly harmless”, though :-)
(“class” arguably sucks in ES2015)
for (let x in list) {
callbacks.push(function () { x+3 });
}
instead of: for (var x in list) {
callbacks.push((function (x) {
function () { x + 3 }
})(x);
}
is a huge advantage to me. (yes, I know arrow function notation exists, but given I was explaining "why I love let" it would've been unfair to use it in the "good" example)OTOH:
list.forEach( function( x ) {
callbacks.push( function () { return x + 3 } )
}
I guess I tend to use forEach, or one of the Ramada.js operations, rather than for loops these days.EcmaScript isn’t Scheme, or Smalltalk/Self, or Ruby. But it sucks a lot less than the other language I’m allowed to use at work :-)
(I pretend that ES is mostly Ruby)
* I'd be curious to hear if @munificent has changed his mind about this article at all since it was written.
Since 2013, JS has added optional lexical scoping and continuations (promises). There is arguably a distaste for mutation in the community and among the major JS frameworks, not sure if that counts.