"I’ve always found it much easier to read code in an editor directly and jump around to understand it." That's Java approach and it seems to be complete opposi

"I’ve always found it much easier to read code in an editor directly and jump around to understand it." That's Java approach and it seems to be complete opposite of literate programming. Code that cannot be read or understood without having an editor and navigation. I personally like to read programs in full, although only rarely there is time to do that. Not exactly literate style, but I like when the documentation is structured hierarchically so I can focus my understanding where I need it. It seems that hierarchical problem decomposition, and the associated programming style (which leads somewhat naturally to literate programming), is out of fashion right now. (It was replaced by mesh of objects, frameworks and microservices.) Maybe it will return back with functional programming. Anyway, to answer authors question - I enjoyed Jones Forth.