Nice ideas. I think that complexity can be the enemy of “hackability.” Some environments like Pharo Smalltalk are simple enough to dig down to see how stuff wo

Nice ideas. I think that complexity can be the enemy of “hackability.” Some environments like Pharo Smalltalk are simple enough to dig down to see how stuff works, and I would add simple Lisp implementations. When I first started using Ruby and Rails, I kept the source code to Ruby and for Rails available for perusal and it was more or less understandable. Not so much now. Complexity. I think that the Racket ecosystem will get more hackable once the codebase sits on top of Chez Scheme. Racket is well documented: 18 months ago I wanted to import trained weights and biases from a trained Keras/TensorFlow model into Racket and implement a runtime - fairly easy to do with good documentation and good library support for fast linear algebra. Too bad that more people don’t spend more effort on hacking activities because really understanding tools, modifying code, etc. is fun and I would argue a good career move. EDIT: added 1 word for clarity