13,831 karma · joined February 28, 2014
I have used gptel a while ago which was great for completion-like workflow, but abandoned when I moved to more agentic stuff.
Claude, the ultimate REPL.
-- Albert Einstein
Blindsight also has augmented humans whose reasoning is beyond baseline human understanding and there are dedicated people that are there to bridge the communication.
yes
funny you say that, because to take advantage of the monstrous bandwidth offered by modern ethernet, OS bypass with the card DMAing directly in your process cache is a must. That reintroduces all the "fun" shared memory ordering issues, except trickier (you are talking with a PCI device, not just another core) and buggier.
Re disk, I'm sure someone will revive optane at some point, and we will be back with memory model issues in our disk I/O path.
The reality is that a programming language that claims to be usable for system programming must be able to deal with shared memory and provide a concurrent memory model.
And of course any sufficiently complicated message passing program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of shared memory and coherency[1].
[1] Yes, the reverse is also true.
At least some GCC devs claimed that the standard does not impose any requirements on these macros if a compiler does not claim strict ISO/IEC 6055 (aka IEE 754) conformance (which is still optional, and gcc and clang do not claim it).
Other devs disagree.
VFIO/GPU passthrough maybe?
energy and resources. Money was always a proxy for them anyway.
DWIM is not a spec.
Usually it means GC, bound checking and no pointer forging.
You are otherwise correct of course.