News for hackers. Stuff that matters.
Re:K (2005) by kick on Thursday January 16, 2020 @12:12AM (#22061847)
k3; 1010data? If so, I'm really curious: has the k3 fork you guys have bifurcated far enough that it no longer resembles k3? It makes me really curious, because substantially modified k doesn't really seem like k much at all anymore.

Things I dislike: [...] APL/J/K "culture",

Ow. It cuts like a knife. Right in the heart! Is it the silly jokes? The bad memes in almost every presentation? That we think our approach is better than everyone else's because it produces better code, faster? That we like math?

Re:K (2005) by ttvecthrowaway on Friday January 17, 2020 @09:45PM (#22081867)
1010er here. I don't think Arthur would have trusted us with a fork if that was even a remote possibility. I find it true to the design and aesthetic of k3--you'd never notice if you didn't use the new features and they seem quite natural.
Re:K (2005) by kick on Saturday January 18, 2020 @01:22PM (#22085999)
Thank you so much for answering! That's fascinating! I hope that at some point someone expands on what features have been added.
Re:K (2005) by rthomas6 on Thursday January 16, 2020 @07:53AM (#22064004)
In what ways is the code better?
Re:K (2005) by kick on Saturday January 18, 2020 @01:40PM (#22086126)
Imagine that you could write something that executed 10x faster, that required half the effort it'd take for you to write something in whatever language you're using right now, that you could reasonably be sure was bug-free, and that would reduce the complexity of your program by an order of magnitude.

None of that is exaggerated; I think most of the comparisons usually have a far higher disparity between Iverson's family of languages and everything else.

There are a few very plausible/simple/not at all "out there" reasons for all of this that I'll explain if you want.