4 ms·
You could do worse than look at user "geocar"'s comment history on HN; he mostly talks about the array language K rather than APL, but he argues a lot about cod
by jodrellblank 5y ago
You could do worse than look at user "geocar"'s comment history on HN; he mostly talks about the array language K rather than APL, but he argues a lot about code size, conciceness, readability, expressivity, etc. more than individual operators or functions. e.g. these and the comment trees around them:
https://news.ycombinator.com/item?id=10876975 https://news.ycombinator.com/item?id=10876975
https://news.ycombinator.com/item?id=8476113 https://news.ycombinator.com/item?id=8476113
https://news.ycombinator.com/item?id=27223086 https://news.ycombinator.com/item?id=27223086
https://news.ycombinator.com/item?id=25484587 https://news.ycombinator.com/item?id=25484587
https://news.ycombinator.com/item?id=25903740 https://news.ycombinator.com/item?id=25903740
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=author%3Ageocar&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
- leprechaun1066 5y agoI am always fascinated by people complaining about decades old programming languages which are still alive and well. Some of those commenters seem to be trying really hard to prove APL and it's offspring are bad/wrong/etc., but history tells us otherwise. Even Numpy relies on the APL family as one of the language groups which guided its design.