kelas

5 ms·

1.
by kelas 11mo ago
oh no, not really. this is not writing in assembly, and definitely not in bytecode. but if you are indeed an elite intel(R) assembly coder, and old enough for eax and rax to have taken too much toll on you, or your time away from your famil
2.
by kelas 11mo ago
author of the annotated version here. > representative example this is grossly taken out of context (which is explicitly stated at the very top of the corresponding readme, https://github.com/kparc/ksimple ). ioccc i
3.
by kelas 11mo ago
> If you're arguing that "Read-Eval-Print cycle" doesn't count as REPL, then it pretty strongly undercuts your argument that "dialog approach". no, thankfully, it doesn't, and here's why. as i eluc
4.
by kelas 11mo ago
this is a gross undeappreciation of a truly remarkable effort by my dear friend and associate. also, at least one of the languages presented is due to him. you can call him @ktye. he's too modest. it is not a Kunstkamera or some comput
5.
by kelas 11mo ago
(well, at least the mf is big in japan now lol)
6.
by kelas 11mo ago
julia is cool, hands down. only typical k binary will be less than 200kb and doesn't need stdlib. it still needs a few syscalls, but we're working on that. and julia has this small and insignificant dependency called llvm. i bulls
7.
by kelas 11mo ago
> Or, do you just not do that sort of stuff in these languages? i tell you more. it is very much recommended to avoid doing this sort of stuff in all languages . v_sepallength: 11 14 12 v_sepallthickness: 1.3 1.5 1.2 mul[v_sepal
8.
by kelas 11mo ago
exactly. the complexity is built differently in k. * namespaces do exist, and are just as useful as they are in c++ and especially my beloved *sun.misc.unsafe*. i recommend. * instead of passing 20 arguments to a function (which is i
9.
by kelas 11mo ago
> t=\:t:!x this is of course obvious first idea, but the recipe from above is actually from the official k4 cookbook. t=t is less innocent than it seems, i'm afraid. in k7/k9, we can: 10^@[100#0.;11*!10;1.] /just fo
10.
by kelas 11mo ago
nice :) also see here: https://news.ycombinator.com/item?id=45603661 HN is such a sweetheart. i should check in more often.
11.
by kelas 11mo ago
> That is wildly disingenuous. assuming you're referring to numpy as to have anything to do with python spec, i totally agree with you. only it doesn't. so don't pytorch and pandas (and good so, poor python doesn't ne
12.
by kelas 11mo ago
ok, you have a point there. all 53 PDP-1s were "cheap" computers compared to IBM stuff (only $1M, adjusted) and used paper drum instead of punch cards. that was a nightmare to deal with, so people were buying IBM M typewriters to
13.
by kelas 11mo ago
for that matter, i always wonder how people mistake python for numpy :) they have surprisingly little in common. but enough talking about languages that suck. let's talk about python! i'm not some braniac on a nerd patrol, i'
14.
by kelas 11mo ago
> without it being tacit, it would probably be more readable definitely. tacit can be taken a bit too far sometimes, but when a certain discipline is observed (just like in any language, really) it is no less readable than... let me see.
15.
by kelas 11mo ago
> seems to disagree no, actually i think Wikipedia got it right: "The 1974 Maclisp reference manual by David A. Moon attests "Read-eval-print loop" on page 89, but does not use the acronym REPL.[7] Since at least the
16.
by kelas 11mo ago
of course it runs in a browser - pretty much everything you can build using clang will run on the web. including linux kernel and llvm itself. to hell with peanuts: i'm pretty sure someone must even built cpython interpreter to wasm ta
17.
by kelas 11mo ago
> your first working program feels like a happy accident. if you don't mind sharing: how did your own first working program felt like, and what was it written in? by the way, did it work, or did it work correctly? it's a small
18.
by kelas 11mo ago
> I'd call that code obfuscation. we call them "trains". since this one has a descriptive name, `avg a`, is not cryptic at all. just a bit fewer of absolutely meaningless parens and duplication. but it doesn't end the
19.
by kelas 11mo ago
guys, symbolic algebra package and a computer language are not the same thing :) not even remotely.
20.
by kelas 11mo ago
i'm sure niall is missing it too :) what does he do these days?
21.
by kelas 11mo ago
in k, we say "primitive operators are verbs", and "lambdas, functions, variables, literals are nouns". higher-order functions (over, scan, each, etc) are called adverbs.
22.
by kelas 11mo ago
> i assume that in most array languages, you also create "words" or however you want to call functions, to reuse code. sure, that's a very useful feature, like elsewhere. > I wonder about a purely aesthetic issue: how d
23.
by kelas 11mo ago
oh, gosh. sorry for your loss. if you don't mind me asking, do you also remember the day when you wrote some non-trivial program in any language and it "worked" the first time, whatever that means (i presume "correctly
24.
by kelas 11mo ago
numpy is also an array language, with a userbase that of (R+k)^10 never seems to make these lists :)
25.
by kelas 1y ago
thanks, and you're welcome. i hope you'll find them useful.
26.
by kelas 1y ago
no, it wasn't your choice how you were taught to read and write something like this: 1|2*3>>4+5 in C and k, this expression should hopefully evaluate to 1, but this is just a lucky coincidence: reading and writing these two expre
27.
by kelas 1y ago
(en passant, k is arguably more lispy than some lisps. for a lisp guy, the first cultural shock is usually the absence of 99% of superfluous parens) as for LLM copilots and the quality of their lisp: why you'd expect them to excel in l
28.
by kelas 1y ago
curiously enough, this thread made me revisit some past conversations with people like atw, nsl and aab with regard to possible ways to expose humans to the way rivers flow in k/q/apl land. the choices are limited, and decision
29.
by kelas 1y ago
No, brother - a neon tube requires at least a 4kV transformer, she's not so easy going. And in 2025 there are still absolutely valid use cases for CRT oscilloscopes, lamp amplifiers, LPs and Compact Cassettes, if you're old enough
30.
by kelas 1y ago
Hard to disagree on the last part, but hand-coding HTML4 for food in 2025 is not the answer. First, it will look horrible. Second, if will look even more horrible on mobiles, which are first . Third, if you're really determined to go

More ›