3 ms·
However, I found the programs being discussed in the J discussion lists completely impenetrable. I would argue that (a big) part of the issue is that proponent
by kd0amg 9y ago
However, I found the programs being discussed in the J discussion lists completely impenetrable.
I would argue that (a big) part of the issue is that proponents often overstate the readability of such code. My usual experience from the J mailing list is that people "read" code by looking at the prose description of what it does, puzzling through how they would do that themselves, and then looking for common structure between the original code and their own reimplementation. It's a good learning experience as far as solving that particular problem is concerned (as there's often more than one way to do it), though it definitely runs counter to the meme that comments and meaningful names are superfluous. The other usual excuse that "the alphabet just isn't the one you're familiar with" isn't really true of mailing list regulars.
- hwayne 9y agoThat's one of the major reasons I think handwriting J is more interesting and understandable than typing it. You can more clearly mark which pieces are conjunctions and what they operate on, you can present the explicit expansion tree as a reference, etc.