3 ms·
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
by jayd16 2y ago
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.
- gmueckl 2y agoCOMEFROM 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.
- Voultapher 2y agoSo I tracked down this programming manual for intercal https://3e8.org/pub/intercal.pdf https://3e8.org/pub/intercal.pdf and can't locate any mention to comefrom.
- mannykannot 2y agoIt 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/intercal.pdf https://www.cs.virginia.edu/~asb/teaching/cs415-fall05/docs/...
- gmueckl 2y agoThanks for that correction! I had memorized COME FROM as part of the original Intercal. My mistake.
- twic 2y agoIt'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 https://esolangs.org/wiki/Threaded_INTERCAL
- eyelidlessness 2y agoThat’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.)