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
Shouldn't this (one way or another) be Ecma-262 specified behavor? I thought we had long ago learned to avoid introducing new implementation dependent JS behaviors.
Replying to @rauschma
New conclusion: Deno’s behavior makes most sense—if it’s certain that a top-level-awaited pending Promise won’t settle (because no tasks or microtasks are active), report an error (vs. silently exiting as Node.js does now). Is there a way to get this behavior for Node.js?
1
4
Allen Wirfs-Brock retweeted
Replying to @senderPath
I remember in the 70s reading P.J. Brown's "Throw-away Compilation" papers in Software Practice&Experience. I was glad to see him mentioned in this "History of JITs" Computing Surveys paper that I had not previously been aware of. eecs.ucf.edu/~dcm/Teaching/C…
1
1
3
"The PDP-1 instruction set is very strange by modern standards." Haha! Every instruction sets of that era are very strange by modern standards Erik's notes bring back great memories of teenage asm hacking in the 1960s. 1/
Made a bit more progress understanding LISP-1 on the PDP-1. Possibly the first REPL published, by L. Peter Deutsch when he was still a teenager. Came across this somewhat WTFy code: The rcl and rar insns do some bit shifting, but first we load a jmp instruction into the IO reg?!
1
1
7
Peter co-invented modern JIT concepts. He's the technical grandparent of everyone who has worked on language virtual machines in the last 40 years. Also an OG Hacker featured in Steven Levy's book amazon.com/Hackers-Computer-…
1
3
"a live system must be allowed to be inconsistent" Words to remember
Ingalls’ beautiful and profoundly humble talk about his life’s work. He reminded me why OOP. Objects extend the set of available types. Inheritance keeps code size down. Types were banished because a live system must be allowed to be inconsistent
2
5
29
An update on the MS Word architectural limitations on outline format lists described in this quoted thread. 1/
Here is an example of a Word bug I discovered that derived from a hidden load bearing architectural decision: The JavaScript standard spec makes extensive use of Word’s outline format lists to specify algorithms. The 2015 edition more than doubled the number of algorithms. 1/
1
2
3
My conclusion is that pandoc is correcting generating the docx file, according to the docx specification. Pages and LibreOffice doesn't have something comparable to Word's 11-bit id limitation so they don't have a problem with all the outline lists. 10/
1
But the latest Word still is still internally limited by a 1980s design decision. When internalizing a docx file, after encountering about 2045 list elements it declares "out of memory" and stops assigning list ids to subsequent list elements. A legacy design bites again. 11/11
3