Introducing command And commandfor In HTML

Re:Introducing command And commandfor In HTML by jayd16 on Friday March 07, 2025 @02:27PM (#43293466)

Maybe I'm lost about the greater theory here. As a non-js dev it looks like they're just adding some OO sugar to events. I hesitate to call it sugar because it seems a lot more verbose than "my-menu.show-popover()" but its better than a global listeners I suppose.

[ Parent | on HN ]

Re:Introducing command And commandfor In HTML by gmueckl on Friday March 07, 2025 @02:55PM (#43293813)

COMEFROM is one of the many great jokes that form the Intercal language. I recommend reading the language specification.

Of course, COMEFROM's grown up (and very real) sibling is ALTER GOTO in COBOL.

[ Parent | on HN ]

Re:Introducing command And commandfor In HTML by Voultapher on Saturday March 08, 2025 @07:05AM (#43299539)

So I tracked down this programming manual for intercal https://3e8.org/pub/intercal.pdf and can't locate any mention to comefrom.

[ Parent | on HN ]

Re:Introducing command And commandfor In HTML by mannykannot on Saturday March 08, 2025 @01:29PM (#43302279)

It is from a dialect called C-INTERCAL and is written with a space: 'COME FROM'

https://www.cs.virginia.edu/~asb/teaching/cs415-fall05/docs/...

[ Parent | on HN ]

Re:Introducing command And commandfor In HTML by gmueckl on Sunday March 09, 2025 @01:06AM (#43306684)

Thanks for that correction! I had memorized COME FROM as part of the original Intercal. My mistake.

[ Parent | on HN ]

Re:Introducing command And commandfor In HTML by twic on Sunday March 09, 2025 @08:48PM (#43315655)

It's also foundational in Threaded INTERCAL, where "multiple COME FROM statements with the same label cause the program to fork separate threads at each COME FROM":

https://esolangs.org/wiki/Threaded_INTERCAL

[ Parent | on HN ]

Re:Introducing command And commandfor In HTML by eyelidlessness on Friday March 07, 2025 @08:24PM (#43296646)

That’s a reasonable analogy, but I think the more novel and interesting thing about this is that it’s:

- A declarative mechanism to relate one element to another

- With a range of semantics for declaring interactivity invoked through their relationship

- At a high level, with explicit guarantees of consistent accessibility and UX

In a lot of ways, this looks a lot like what people describe when they wish for more HTML and less JS. (Except for the extreme-minimalist version of that which rejects web interactivity altogether.)

[ Parent | on HN ]