4 ms·
I think I still mostly agree with it. let was on the way in when I wrote that, but that doesn't mean lexical scoping is a particularly interesting or defining t
by munificent 9y ago
I think I still mostly agree with it. let was on the way in when I wrote that, but that doesn't mean lexical scoping is a particularly interesting or defining trait of JS. Most languages today have pretty solid lexical block scoping, so that's more JS playing catch-up than anything else.
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-your-function/ 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.)
- DonHopkins 9y agoINTEGER BASIC or APPLESOFT? ;)
- munificent 9y agoFirst were Applesoft BASIC on my Apple IIe at home, and whatever weird BASIC ran on the TRS-80s at school. Then Microsoft QuickBASIC on an early Mac, followed by FutureBASIC, mostly on a Mac LC. There was a little RealBASIC near the end before I finally switched over to C. 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.
- adrianratnapala 9y agoBASIC was my first programming language too. And I hated it from the moment the thrill of being able to program a computer at all wore off. It kept creating itches in me that I couldn't scratch, or even name until I dove into Pascal and, later C. 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).