Allen Wirfs-Brock

@allenwb
905 Followers
149 Following
396 Posts

Dreaming the future of software; Project Editor of the ECMAScript 2015 Language Specification; Reformed Smalltalker.
JavaScript historian: https://dl.acm.org/doi/abs/10.1145/3386327

Everybody needs a Personal Digital Habitat!
https://wirfs-brock.com/allen/posts/1033

Webhttps://wirfs-brock.com/allen
Google Scholarhttps://scholar.google.com/citations?user=4e9hfecAAAAJ

RE: https://mastodon.social/@wingo/116294319311502266

Very interesting. A concern is that there is an implicit assumption that Test262 actually has 100% test coverage of the relevant Ecma specs. In theory, it should cover every externally observable requirement that is expressed in the spec algorithms and prose. That's was an asperational which as far as I know is yet to be achieved.

This suggests another interesting experiment: could Claude Code, starting with the specs, generate a new version of Test262 with more comprehensive coverage.

raven-uxn now has an x86-64 assembly backend (yay!)

and it's about 2x faster (yay!!)

and the first draft was written by Claude (booo!)

and then I rewrote most of it, which made it even faster (yay!)

and introduced a memory corruption bug (booo?)

which Claude is better at debugging than I am (.......?)

--------

if you too have complicated feelings about our robot buddies, you may enjoy my writeup:

https://www.mattkeeter.com/blog/2026-03-15-uxn/

An x86-64 backend for raven-uxn

Porting 2000 lines of ARM64 assembly to x86-64, with the help of a robot buddy

“Earlier today, Temporal reached Stage 4 in the TC39 staging process, which means it will be part of the next annual ECMAScript specification (ES2026). However, you don't need to wait until then – you can use it today!”
https://bloomberg.github.io/js-blog/post/temporal/

#JavaScript

Temporal: The 9-Year Journey to Fix Time in JavaScript

JavaScript's Date object has been a source of bugs for three decades. Temporal, which just reached Stage 4, is a modern replacement with immutable types, first-class time zone and calendar support, and nanosecond precision. This is the story of how Bloomberg, Igalia, and the TC39 community spent nine years turning an idea into a shipping standard.

Bloomberg JS Blog

If you are an author whose work is on the ACM DL, I'd like to strongly encourage you to check the accuracy of the AI Summary of your paper, and send feedback to the ACM on this feature and the inaccuracies in your summary. See more here: https://dl.acm.org/generative-ai/summarizations

Please boost, repost, and otherwise steal this post to reach other authors.

In long:

The ACM has begun rolling out "Digital Library Premium" features. A very notable one is AI Summaries of papers, which displace the author written abstract with an AI generated summary of the paper on the front page for the paper.

Of the several I've checked, they all contain subtle inaccuracies that would VERY EASILY mislead even experts familiar with the work.

This is a HUGE DISSERVICE TO SCIENCE. These summaries might appear to make science more accessible, but subtle errors introduced into the authors original text is the very opposite of making science more accessible. This will mislead rather than educate.

The ACM has a feature to send feedback on these summaries. Open your DOI, and look for the "Feedback" button on the right of the page, or the "Send Feedback" link in the footer. (You might need to disable ad-blockers, as this services uses mopinion.com)

The ACM is requesting this feedback, and it's important to let them know that such "hallucinations" are not solvable:

These tools were designed in consultation with a diverse group of Digital Library stakeholders and will continue to evolve as Artificial Intelligence advances. We are continuously tuning our Foundational Model to optimize readability and we conduct regular audits for hallucinations and other errors. We are very interested in your thoughts and suggestions- please leave them by clicking the "Feedback" button on the far right of this page. If you find a problem with a specific AI-generated summary, please return to that summary and click the Feedback there.

More aggressively, you might email [email protected] (also linked in the footer).

Update 1: It seems the ACM no longer displaces the abstract with these summaries, so I can hope this feedback has been helpful in affecting change.

Update 2: It seems these summaries have been generated on papers whose license may forbid it, such as CC-BY-ND. If you have a restrictive license on your paper, you may check whether it’s being followed and send further feedback if not.

Bring Back Innovation That Empowers, Rather Than Extracts: The Resonant Computing Manifesto

Everyone’s pissed at the tech industry. And for good reason. The term enshittification is super popular for many valid reasons. Companies that used to provide real value, are now focused on e…

Techdirt

This very much resonates with me.

Includes an unexpected mention of "QWAN"

https://resonantcomputing.org/

The Resonant Computing Manifesto

Technology should bring out the best in humanity, not the worst—a manifesto for resonant computing built on five principles that reject hyper-scale extraction for human flourishing.

I declare that today, Nov. 19, 2025 is the 50th anniversary of BitBLT, a routine so fundamental to computer graphics that we don't even think about it having an origin. A working (later optimized) implementation was devised on the Xerox Alto by members of the Smalltalk team. It made it easy to arbitrarily copy and move arbitrary rectangles of bits in a graphical bitmap. It was this routine that made Smalltalk's graphical interface possible. Below is part of a PARC-internal memo detailing it:
Revisited my position statement from the Substrates 2025 workshop back in June, and found it somewhat better than I remembered... here is a tiny blog post to introduce it. https://www.humprog.org/%7Estephen/blog/2025/09/12#substrates-should-there-be-only-one
Rambles around computer science

Thanks to 20+ years of cooperation via standards, most web devs are insulated from the reality that competition (or the threat of it) makes standards possible. It's a shock to recognise that Apple has broken the system so thoroughly that SDOs themselves are at risk:

https://infrequently.org/2025/09/apples-crimes-against-the-internet-community/

Apple's Assault on Standards

By subverting the voluntary nature of open standards, Apple has defanged them as tools that users might use against the totalising power of native apps in their digital lives. This high-modernist approach is antithetical to the foundational commitments of internet standards bodies and, over time, erode them.

Alex Russell