14,716 karma · joined June 25, 2013
"Visual FoxPro is a 32-bit program, and that decides more than it appears to. It is why a table stops at two gigabytes, why a memo file stops at two gigabytes, and why a big report runs out of memory on a machine with plenty to spare. The limits are signed 32-bit numbers buried in the file handling, not a licensing decision anybody made."
and
"The editor checks what you type through that very compiler, so what it underlines and what the runtime refuses cannot drift apart."
Like, what? Who talks like that?
(I do think Pi should ship with more than zero builtin sandboxing though)
ai; dr, sorry
https://serotav.github.io/Writeups/v8/when-sorting-leads-to-...
That's not a great summary of what happened with the invention of the H-bomb.
I am certain that plugging a circa 2023 model into a 2026 harness would be a pretty frustrating experience. Yes, you could code a bit with AI in 2023, but models are just much better at it than they used to be. And smaller open models are leaps and bounds better at it than they were three years ago.
https://electronicbookreview.com/publications/constructing-t...
LLMs have never been the place I've thought to expect any commitment to the craft of writing, to be fair.
I think this is one reason why LLM text is pretty exhausting to read for long stretches.
or use just use actual files instead of pipes with a permissions dialogue gate on write. That would work already in Claude I think, and with IDE integration it would show each step as it went.
Of course buffering every step of a pipeline will have its own side-effects.