Conversation
kopper 
kopper@not-brain.d.on-t.work
compilers are bourgeois, jits and interpreters are proletariat. i will not be taking questions
1
0
0
@kopper jits are bourgeois too , interpreters are cool
2
0
0
2
0
2
0
0
1
@snacks @fiore @kopper the majority of implementation (direct and indirect threaded code) use this and even subroutine threaded code works similarly but leveraging actual processor instructions in place of the interpreter (at the potential slight expense of memory since subroutine instructions arent as compact as execution tokens)
0
0
0
@snacks @fiore @kopper geforth does not use subroutine threaded code, it does actually have a really convoluted interpreter that uses a mix of both direct and indirect threaded code
this is one of the things i dont like about it and why id like to hack around on pforth instead but to be perfectly honest ocaml or sml might be the better choice in the long run
this is one of the things i dont like about it and why id like to hack around on pforth instead but to be perfectly honest ocaml or sml might be the better choice in the long run
1
0
1
@coolbean @fiore @kopper yeah, gforth is an abomination, pforths main disadvantage is gonna be that it's slow as balls in exchange for being very hackable and easy to understand.
I welcome any exploration into languages that arenct plagued by trying to be like c and lose the weird shit that comes with it's syntax
I welcome any exploration into languages that arenct plagued by trying to be like c and lose the weird shit that comes with it's syntax
1
0
1
only the SICP meta-circular evaluator is truly revolutionary
CC: @kopper@not-brain.d.on-t.work @fiore@brain.worm.pink
CC: @kopper@not-brain.d.on-t.work @fiore@brain.worm.pink
0
0
1