I never noticed the disclaimer at the bottom until today
xkcd.com is best viewed with Netscape Navigator 4.0 or below on a Pentium 3±1 emulated in Javascript on an Apple IIGS
at a screen resolution of 1024x1. Please enable your ad blockers, disable high-heat drying, and remove your device
from Airplane Mode and set it to Boat Mode. For security reasons, please leave caps lock on while browsing.
Prediction: someone will make a reverse polish notation skill for interacting with claude claiming all sorts of things, like caveman, turn into another markdown as a service company, and make the news.
See Self's "dynamic deoptimization", where it constructs a virtual return stack on demand that you would have had, were it not for the JIT compiler's agressive inlining.
Debugging Optimized Code with Dynamic Deoptimization, by Urs Hölzle, Craig Chambers, and David Ungar:
A different way to say the same: in forth, words get pushed on the stack, and popped from the stack by words that take arguments:
code stack
I Forth love
Forth love I
love I
Forth
; love presumably pops
; subject, object args
; from stack - and does something
; perhaps prints as side effect
Even oddly more pedantically, that's the operand stack, not to be confused with the separate return stack. >R and R> move values between the two stacks.
On the other hand, PostScript also has a dictionary stack, which you can use to implement a Smalltalk-like object oriented programming system. And its data types and executable code are basically polymorphic homoiconic JSON (like Lisp), not raw untyped bytes like FORTH.
Slightly OT, but nothing can beat DonHopkins’s “About” section here on HN [0].
0: https://news.ycombinator.com/user?id=DonHopkins
FORTH LOVE? IF HONK THEN
I never noticed the disclaimer at the bottom until today
Also, the font chosen is all capsPrediction: someone will make a reverse polish notation skill for interacting with claude claiming all sorts of things, like caveman, turn into another markdown as a service company, and make the news.
I present to you, the return-stack skill:
https://github.com/SimHacker/moollm/tree/main/skills/return-...
See Self's "dynamic deoptimization", where it constructs a virtual return stack on demand that you would have had, were it not for the JIT compiler's agressive inlining.
Debugging Optimized Code with Dynamic Deoptimization, by Urs Hölzle, Craig Chambers, and David Ungar:
https://bibliography.selflanguage.org/_static/dynamic-deopti...
And a return-stack rotated 180 degrees around in time is an action-queue:
https://github.com/SimHacker/moollm/tree/main/skills/action-...
From games like The Sims:
https://sims.fandom.com/wiki/Action_queue
Also the ever popular advertisement skill, more like comefrom than goto:
https://github.com/SimHacker/moollm/tree/main/skills/adverti...
Also from The Sims:
https://simstek.fandom.com/wiki/SimAntics
The Sims, Pie Menus, Edith Editing, and SimAntics Visual Programming Demo:
https://www.youtube.com/watch?v=-exdu4ETscs
Amazing
Saw the same joke with Postscript many years ago.
Can someone explain for me?
A different way to say the same: in forth, words get pushed on the stack, and popped from the stack by words that take arguments:
Is that loss?
Here is some inexplicably but meticulously formatted FORTH code that uses right justified indentation! Including reverse polish notation assembley.
https://donhopkins.com/home/code/tomt-cam-forth-scr.txt
https://donhopkins.com/home/code/tomt-users-forth-scr.txt
Forth I assume uses reverse polish notation: arguments before the operator.
3 4 +
for example, would return 7.
> would return 7
more pedantically, it would push 7 onto the stack
even more pedantically, would remove 3 and 4 from the stack before pushing 7
Even oddly more pedantically, that's the operand stack, not to be confused with the separate return stack. >R and R> move values between the two stacks.
On the other hand, PostScript also has a dictionary stack, which you can use to implement a Smalltalk-like object oriented programming system. And its data types and executable code are basically polymorphic homoiconic JSON (like Lisp), not raw untyped bytes like FORTH.
https://news.ycombinator.com/item?id=22456471
https://news.ycombinator.com/item?id=47812317
The stack is really a convenience that makes pipeline-driven programming possible in the language.
Forth uses RPN so the "verb" is last.
That is, you provide the data first (I and Forth) and the command (heart) last.
I found https://www.explainxkcd.com/wiki/index.php/Main_Page quite useful for that.
That beautiful is.
I first thought this was some spin on May the fourth be with you. As in how Yoda might say it.