3 ms·
I think I'd rather have a half page of APL with a page of explanations (given a little time to learn the language better than I do now) than 20 pages of Java th
by 7thaccount 3y ago
I think I'd rather have a half page of APL with a page of explanations (given a little time to learn the language better than I do now) than 20 pages of Java that I have to scroll through with comments and unintelligible class paths.
Either way it takes time to consume the logic, but it's nice to have it all in one place than scattered about all over creation. I think that's what he's getting at with Aaron's more macro based view. He wrote thousands and thousands of loc before being able to whittle it down to such a terse amount. I can't read it, but that's less to do with APL and a lot more to do with knowing nothing of the domain of compilers.
The symbols actually make a lot of sense and can help you remember what they do. I can remember quite a few after only playing around with it a bit and reading a book on it ages ago.
- ryan-duve 3y agoDo you remember which book it was you read?
- 7thaccount 3y agoFor APL I started with the Mastering Dyalog APL book they have for free on their website which is good, but long. Someone recommended an ancient book I found on Amazon called "APL An Interactive Approach 2nd Ed." I think by Gilman and Rose that is very easy to follow. There are plenty of tutorials online now too (a lot more than when I started looking 8 years ago). For J, I read a good bit of "Numerical Programming in J" or something along those lines. I've found J to be more difficult than APL or K to pick up tbh. The tacit trains is just a bit too hard for me to follow.