Why the fuck make a tech web page unreadable with CRT effects? Thank god, there is reader mode in Firefox.
Tail-Call Interpreters in Rust – Jimmy Ostler
11–20 of 35 posts
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#12Why the fuck make a tech web page unreadable with CRT effects? Thank god, there is reader mode in Firefox.
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#13Ctrl-Shift-C, click on a paragraph, search for "text-shadow" on the right pane of the inspector, untick the checkbox. There is a time and place for text and retro-CRT effects, this isn't one.
Thank you. I was about to get eye cancer
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#14Another thing that is kinda neat: there is a duality (a bidirectional transform) between the AST for a tree walking interpreter and the AST for a stack machine. To create the stack machine AST, all you do is remove any occurrence of the expression type in the tree-walking AST; these values are now found on the stack. Obvious when you think about it, but useful nonetheless. I don't think there is a simple equivalent for a register machine as, unless you have an infinite number of registers, you need to do register allocation.
(If the author reads this, my name changed from Noel to Neal at some point. I don't really mind though; my name is a bit unusual and I've been called all sorts of things.)
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#15Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#16Why the fuck make a tech web page unreadable with CRT effects? Thank god, there is reader mode in Firefox.
YMMV, but OP, if you read this, please consider disabling the text-shadow for code snippets... or disabling syntax highlighting in code snippets. These two things are not a good thing together.
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#17Made my day that it references an article I wrote! :-D Another thing that is kinda neat: there is a duality (a bidirectional transform) between the AST for a tree walking interpreter and the AST for a stack machine. To create the stack machine AST, all you do is remove any occurrence of the expression type in the tree-walking AST; these values are now found on the stack. Obvious when you think about it, but useful no…
If I may leave some feedback here...
It'd be cool if you could add some syntax highlighting, because being at it is, it's hard to distinguish comments from code paths. The code snippets are just Scala anyway, aren't they?
Why, in the switch dispatch- and the subroutine threading-variants, is the recursive call in the dispatch function done with a call to loop(...)? Is that some Scala specific thing for recursion?
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#18Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#19Why the fuck make a tech web page unreadable with CRT effects? Thank god, there is reader mode in Firefox.
I actually find it quite readable - YMMV.
Bringing the brightness levels of the background and text closer together doesn’t ever seem to work, but being able to add a slight blurry dropshadow behind behind each character might be a way to reduce the artifacts OLEDs seem to create when my eyes are tired.
Re: Tail-Call Interpreters in Rust – Jimmy Ostler
#20Ctrl-Shift-C, click on a paragraph, search for "text-shadow" on the right pane of the inspector, untick the checkbox. There is a time and place for text and retro-CRT effects, this isn't one.