skruger

6 ms·

1.
by skruger 2mo ago
Cormac McCarthy gets my vote.
2.
by skruger 2mo ago
The 'unit of thought' thing is a nod to the Ken Iverson paper on APL that won him the Turing Award ("Notation as a Tool of Thought"), also referenced by Dyalog's tag line "The tool of thought for software solut
3.
l: A new runtime for k and q(lv1.sh)
178 points by skruger 2mo ago|113 comments
4.
Cathy Tie's mission to genetically modify babies(theguardian.com)
4 points by skruger 4mo ago|0 comments
5.
by skruger 4mo ago
It has a huge RoI, even if you never use it in anger. It’s a bit like Lisp in that regard — it shapes your thinking.
6.
by skruger 4mo ago
A more concise intro to APL for the modern era: https://xpqz.github.io/learnapl (author)
7.
History of CRMs APL(computer.org)
2 points by skruger 6mo ago|0 comments
8.
by skruger 8mo ago
I faced exactly this situation a few years ago - I went with APL as the “OG”, but it probably doesn’t matter that much. Learning k or j once you know APL is much easier. I wrote a bit about this (apl and k) https://xpqz.github.io
9.
by skruger 8mo ago
It makes parsing tricky. But for the programmer it’s rarely an issue, as typically definitions are physically close. Some variants like BQN avoids this ambiguity by imposing a naming scheme (function names upper case, array names lower case
10.
by skruger 8mo ago
Yes, it's either an array (if A, B and C are arrays), a function derived via the dyadic operator B, with operands A and C being either arrays or functions, a dyadic function call of the dyadic function B (A and C are arrays), or the se
11.
by skruger 8mo ago
Whilst LLMs still perform weakly in APL, the situation is improving at pace, and giving it a “skill” to evaluate code makes a dramatic difference. I gave a conference talk about it recently (video): https://youtu.be/H_wdKeJ8
12.
Dark energy got even weirder(bbc.co.uk)
8 points by skruger 9mo ago|1 comments
13.
GPU Array Programming with Parrot(nvlabs.github.io)
1 points by skruger 11mo ago|0 comments
14.
by skruger 11mo ago
Start here: https://xpqz.github.io/learnapl or here: https://xpqz.github.io/kbook
15.
by skruger 1y ago
QinetiQ?
16.
Water sommeliers rival wine terroirs(theguardian.com)
3 points by skruger 1y ago|0 comments
17.
by skruger 1y ago
The author also wrote an APL for Plan9: https://apl.pmikkelsen.com/
18.
Science is winning the Tour de France(msn.com)
1 points by skruger 1y ago|0 comments
19.
by skruger 1y ago
As to the training set's depth of APL, yes, it's an issue. However, it's worth seeing how well MoonBit[1, 2] works with LLMs, faced with exactly the same problem -- integrating the LLM directly into the parser pipeline. 1: h
20.
by skruger 1y ago
The learning curve isn’t steep. I’d argue the opposite. K is a tiny, tiny language. Put your mind to it, and you’ll be reading it just fine in a weekend. It’s just different. It’s optimised for its wheelhouse.
21.
by skruger 1y ago
Here is a gentle start: https://xpqz.github.io/kbook/Introduction.html
22.
by skruger 1y ago
https://xpqz.github.io/learnapl/_images/threelamps.png
23.
Do programming languages deliver on their promises? [video](youtube.com)
1 points by skruger 1y ago|0 comments
24.
by skruger 1y ago
Would you mind sharing what you did? stefan@dyalog
25.
by skruger 1y ago
Thanks for saying that. I will update it at some stage for the new array notation stuff.
26.
by skruger 1y ago
Should you ever decide to take that leap, maybe start here: https://xpqz.github.io/learnapl (disclosure: author)
27.
IBM to Acquire DataStax(newsroom.ibm.com)
6 points by skruger 2y ago|0 comments
28.
by skruger 2y ago
That’s nice of you to say so.
29.
by skruger 2y ago
How’s your Korean?
30.
by skruger 2y ago
Yeah—true. I wrote it as “the missing manual” for ngn/k, enough to get someone over the initial hump. It’s not a “Mastering k” tome.

More ›