3 ms·
Perhaps the approach to maintaining a large codebase of terse code (such as J) is to keep the files very small and narrow in focus. This could end up very simil
by chongli 7y ago
Perhaps the approach to maintaining a large codebase of terse code (such as J) is to keep the files very small and narrow in focus. This could end up very similar to a Unix userland code tree.
Of course, lots of documentation could also help. Maybe a style similar to R/Python notebooks would work.
- gmfawcett 7y agoThat's an interesting point. I wonder if the small, focused approach is (or was) common in professional APL/J/K development. It turns out that there is a Jupyter notebook implementation for J [1]. I might play with that! I suspect that you're right, notebooks would be a good fit for terse languages. [1] https://code.jsoftware.com/wiki/Guides/Jupyter https://code.jsoftware.com/wiki/Guides/Jupyter