3 ms·
I'm quite amazed how the author has not made any mistake in the presentation. I wonder if using APL leads to a different state of mind where tool is out of your
by notimetorelax 13y ago
I'm quite amazed how the author has not made any mistake in the presentation. I wonder if using APL leads to a different state of mind where tool is out of your way or was it simply a well rehearsed demo?
- X4 13y agoMy prof also writes complex APL code live and I've never seen a program he made that didn't run or had a bug. He has a I ❤ APL sticker on his laptop. And he is a god damn genius, we can't compare us to him in absolutely no, no way. It doesn't lead to a different state of mind, that guy was already born a genius a little like rainman, but without the downsides. He switched to J after I showed him that a few years ago and is ever happy since. He told me that he paid about 2000bucks for his APL compiler back then.
- sz4kerto 13y agoIt does. I programmed in an APL 'derivative' (Q) for a while, it's quite easy to get the hang of it. The problem is that it's write only.
- keithpeter 13y agohttps://github.com/kevinlawler/kona https://github.com/kevinlawler/kona Kona is free and would give people a flavour of this style of programming (minus the database tools). http://www.jsoftware.com/ http://www.jsoftware.com/ J is mentioned by another poster below (EDIT) Grandparent post: if you are half a bagel and a housebrick, this stuff makes me feel like a few grains of sand and a peanut.
- Q6T46nT668w6i3m 13y agoI suspect it was mostly the later. ;) Nonetheless, because array programming requires unorthodox input and is sufficiently different than popular paradigms, authors typically write slower which may explain the deliberateness.