yeah the site's clearly vibecoded and isn't opensource, but i also think this is a genuinely interesting design space and more people should be building in it. APL ( https://www.dyalog.com/ ), BQN ( https://mlochbaum.github.io/BQN/ ), J/Jd ( https://code.jsoftware.com/wiki/Jd/Overview ), Klong ( https://news.ycombinator.com/item?id=10586872 ), Kerf ( https://news.ycombinator.com/item?id=9782520 ), RayforceDB ( https:…
... DuckDB. Columnar databases are array languages, after all.
l: A new runtime for k and q
61–70 of 118 posts
Re: l: A new runtime for k and q
#62Earlier quoted context omitted.
Fair enough. Without seeing the code itself, one can only judge the book by its cover. I'm interested, but maybe not quite the target audience.
Unfortunately the code itself is in a style of C many find difficult to read. I blame my upbringing. ATW open sourced examples and it was not really helpful. More recently others are doing a step by step in more standard C https://github.com/ardentsia-cgs/kparser/
Re: l: A new runtime for k and q
#63Re: l: A new runtime for k and q
#64I thought too long to find out what a means in a new runtime.
Re: l: A new runtime for k and q
#65Re: l: A new runtime for k and q
#66If this kind of thing interests you, you can try KlongPy (based on Klong) which also now has backprop support making it a differential array language.
Re: l: A new runtime for k and q
#67We'd like to see some benchmarks against open and closed k interpreters please! I'm curious how well a vibe coded k/q interpreter stands up to Shakti or whatever Mr. Whitney is letting out the door right now.
Re: l: A new runtime for k and q
#68yeah the site's clearly vibecoded and isn't opensource, but i also think this is a genuinely interesting design space and more people should be building in it. APL ( https://www.dyalog.com/ ), BQN ( https://mlochbaum.github.io/BQN/ ), J/Jd ( https://code.jsoftware.com/wiki/Jd/Overview ), Klong ( https://news.ycombinator.com/item?id=10586872 ), Kerf ( https://news.ycombinator.com/item?id=9782520 ), RayforceDB ( https:…
I hope OP can survive the lawsuits though, the K authors are infamously litigious.
Re: l: A new runtime for k and q
#69yeah the site's clearly vibecoded and isn't opensource, but i also think this is a genuinely interesting design space and more people should be building in it. APL ( https://www.dyalog.com/ ), BQN ( https://mlochbaum.github.io/BQN/ ), J/Jd ( https://code.jsoftware.com/wiki/Jd/Overview ), Klong ( https://news.ycombinator.com/item?id=10586872 ), Kerf ( https://news.ycombinator.com/item?id=9782520 ), RayforceDB ( https:…
What's the problem if a site is vibecoded? We will be seeing it more often, I recon. Let's get used to it. On the other hand, perhaps a disclaimer is in order.
Typically if a site is well designed, that used to be a signal that a lot of resources had been invested into the project. Now that signal is rather noisy.
Here, is particularly bad, as the main page is just complete slop bullet points. What does 'end-to-end column compression' mean? or 'uniform bytes at every layer'?
It's difficult to understand at a glance now, if this project is going to be abandonware in a week or if someone actually spending time on this. If the creator can't be bothered to read it, why should I?
Personally, I'm also very weary of Claude design-isms. Once you learn them, you see them everywhere.
Re: l: A new runtime for k and q
#70Memory got faster, no?