876 karma · joined January 17, 2023
bump up to EmbeddedLinux and i think Rust wins ovr C
You should try. There’s a difference in kind between approving each tool use and spinning up an all-night session with full permissions to run any tools, encouraged to run subagents to preserve context.
I have no idea how it’s implemented. Lua goes in, position-independent dependency-free xTensa LX7 code comes out the other. Maybe I should read the code?
It’s extremely fast. 3kB of lua becomes 1kB of machine code. I’ll have to get a blog post together on it.
But, when working on a creative graphics task, the results were best in Lua, middling in integer-only C, and underwhelming in ASM in terms of creative depth.
That’s why I’m so concerned about Bluetooth
tl;dr: ___human-written____
____claude blob here_____
Where the idea is that humans only read human writing, and Claude is able to share context between sessions with the jargon-riddled blobs.
Trouble is, I catch people every day blatantly writing the Tl;dr with Claude or ChatGPT.
Indeed it seems quite possible we are one architecture breakthrough away from existing chip stock driving us all the way to ASI.
Nobody has done AFAIK the information theory to prove it’s not possible.
Take the “train” portion of tasks on some benchmark, have K3 complete it, and then output detailed descriptions of tools used and why, then run the validation tasks with some small model that has access to the skills.