NeXeNthe older i get the less Fs i give about what framework, language, or library i am using, as long as it doesn't have a lot of CVEs and stuff for me to patch up
NeXeNsometimes i forget and have to check the language i'm using.....
jreicherWe should all go back to Smalltalk
NeXeNyou know, true a true lisp machine (sort of but not related to lisp the language) has a wonderful feature where everything is a tree, and your codepath is a bunch of Ys and where data goes in or out is a dangling end on the Y connected to that function that either emits or sinks it
NeXeNi forget who invented it, but it was replaced by the current type of machine, von neumann i believe
jreicherHe had a hand in it. Princeton architecture is probably what you're thinking of.
jreicherBut Backus blamed him.
NeXeNespecially because it was a recursive, which will blow your memory up. having a stack and a heap is a nice design alternatively
NeXeNbut i love the design of it's simplicity to solve problems, and i think one could code a system like that it just has to be modern in it's approach to memory management
deeboany known good replacements for easy-random, to generate random object trees using records?
deebofound at least k-random, a kotlin fork of it that works partially