Dreaming the future of software; Project Editor ECMAScript 2015; Reformed Smalltalker JavaScript historian dl.acm.org/doi/abs/10.114@allenwb@mastodon.social

Sherwood Oregon USA
They are standard built-in “classes” and the design of ES6 class declarations is directly based upon the structure of those “classes”. 1/
Replying to @laurieontech
Also have to point out, TC39 itself lacks technically correct terms for lots of stuff. Every time I've presented Temporal I've referred to it as a set of new types for date and time. It's not really new types though. But nobody knows what else to call it! So types.
2
3
5
Object-think is fundamentally about identifying, naming, and reasoning about computatinal abstractions (i.e. classes) that manifest multiple descrete “instances” that share a common behavior. /6
1
2
IMO, a major failing of the “prototypal” approach is the lack of terminology for naming/discussing/reasoning about a set of objects that share a common behavior. (and “type"s is not a good substitute as it carries too much additional baggage) 7/7
4
1
6
I think the naming choices for let and const was indeed a mistake. For ES6, we carried forward, without critical review, the naming choices made as part of the aborted ES4 effort. But note that "const" had been present as a immutable "var" in SpiderMonkey since 2000 (JS1.5) 1/
6
3
22
If we thought that block scoped assignable declarations were actually needed we could have added them using a name such as 'letvar' or perhaps as a prefix 'let var'. In either case, the semantics would be the same as ES6 'let'. But I think we would be fine without it. 4/
1
7
When we committed to the names 'let' and 'const' for ES6 we thought we were following good precedence and that we were constrained by the available reserved words. Only later after resolving 'let' compatibility concerns did we understand we could compatibly choose other names 5/5
1
4
Who was the grad. student? They should be listed in the annals of programming! (if it existed)
Replying to @vgr
1. Johnny Von Neumann isn't nearly as deep a genius as people seem to think. If he was, he wouldn't have said bullshit like this
1
3
21
What I learned today was that my circa 2000 decision to stop bringing overhead projector transparancies for my talks may have been premature.
Would it be a conf without some tech difficulties 😂. Props to @awbjs for taking to the stage without access to his speaker-notes annndddd winging it like an absolute boss #GoBlueRoom #yow19 @yow_conf @awbjs - JavaScript: Skeletons in the closest
9
"Boomer binging" Watch two episodes per night and immediately fall asleep.
1
4
Allen Wirfs-Brock retweeted
RT @unixbigot: The live transcription of the @awbjs talk on JavaScript just transcribed “double equal” as “devil equal”. This is now my headcanon. #yow19
1
4
This sort of unnecessary fabricated intellectual conflict is the bane of our profession
I've noticed that functional programming adherents get turned off by the *keyword class* much more than any particular aspect of OO programming. In contrast, people who like object oriented programming don't have a visceral dislike for the keyword function.
1
13
34
Hey, I’m Dec. 6 on the 2019 Smalltalk advent calendar. javascript.christmas/2019/6
2
3
16
Allen Wirfs-Brock retweeted
I'll be giving a short talk at this meetup on using Secure ECMAScript to secure... a light bulb. Not a talk about how it might work, but a real commercial light bulb (hacked!) running SES in XS by @moddabletech. I think this is my 4th talk built around a lightbulb this year...
We are hosting our first SES Meetup today! 🎉 Read and learn about SES here 👉medium.com/agoric/ses-securi… and if you wish to attend, please RSVP here eventbrite.com/myevent?eid=8…
2
11
21
I didn't wear my turkey hat running...but along with @awbjs @jordanwb and Ben Zeiger we ran in the Sherwood Give'n Gobble race. My very slow 10k time was at a 12:31 pace. But at least I burned some calories today
1
4