> As this thread and post proves, quite a lot of people have no issue reading + understanding it.
This thread, like this implementation, is a troll, a joke, and everyone trying to appreciate this thing as a language is being pranked.
This thread, like this implementation, is a troll, a joke, and everyone trying to appreciate this thing as a language is being pranked.
However it does not naturally scale to teams. But each way of working has its own strengths and weaknesses; if you are aiming for large teams working together on large projects, I would not recommend this. That is not because of readability, but because the code is so terse that you would, even with 2 people, be changing the same code a lot of the time, so it's more efficient to do it alone or in pair programming (which does work well; also remotely in an APL-like in my experience).