I think what the author is trying to say is that the turboencabulator's vertex manifold buckler dimensional engine leverages bifrontal synergies spanning several plasmic thresholds.
This enables an Agentic Solution Plexus to surplant inter-connectomic data access completely locally over the internet, securely, in a federated sandboxed reinforcement learning evolutionary cow-milk optimisation harness, complete with Lorentz-Newton manifold compatible titanium bearings.
You will get MUCH more uptake and discussion if _you_ write that main github readme page. Many, and I’m becoming one too, won’t bother reading if you couldn’t be bothered to write.
"That concentration is an architectural choice rather than a law of physics" except it's entirely based on the laws of physics. The closer you are, the faster the communication lane.
Went through the Readme, the direction you point out is exciting but i still wonder what it communicates? would love to know your personal opinion what you try to accomplish here?
What is the point of a "README" when no one is going to read that wall of slop.
As soon as I see the common AI fingerprints "No X, No Y", excessive use of commas, and extremely short sentences, it is likely that the author hasn't read the document and it now becomes a DONTREADME.
I think what the author is trying to say is that the turboencabulator's vertex manifold buckler dimensional engine leverages bifrontal synergies spanning several plasmic thresholds.
This enables an Agentic Solution Plexus to surplant inter-connectomic data access completely locally over the internet, securely, in a federated sandboxed reinforcement learning evolutionary cow-milk optimisation harness, complete with Lorentz-Newton manifold compatible titanium bearings.
Sounds exciting!
You will get MUCH more uptake and discussion if _you_ write that main github readme page. Many, and I’m becoming one too, won’t bother reading if you couldn’t be bothered to write.
[flagged]
This seems a little, messy?
is the readme aimed at humans? because its a bit scatter gun.
Is it a model orchestrator? or a wrapper around docker/nix/cgroups+chroot?
Like what makes it an OS?
You rightly point out that shared memory across wifi/crappy ethernet is a bad idea, but then how do you get around that?
He asked codex to build this. He does not even know what it means when people say the term OS
[flagged]
"That concentration is an architectural choice rather than a law of physics" except it's entirely based on the laws of physics. The closer you are, the faster the communication lane.
[flagged]
Went through the Readme, the direction you point out is exciting but i still wonder what it communicates? would love to know your personal opinion what you try to accomplish here?
[dead]
Curious about where this is most applicable
Nowhere.
The guy that asked an agent to build this does not even know what an OS is
Can you estimate how much it'd cost to make? Having ^F'ed "Load-bearing" I determined it must have been Claude
And! If you think the github is cancer. See the website: https://hevolve.ai/
Catastrophic loss of izzat
just subscribed
oh boy
[flagged]
Calling this shit an OS, is a logic jump that no computer science engineer would do. But hey, we're living AI slop times.
Wow. So this is what a codebase looks like if you just had "come up with 3 improvements" running in a loop.
TempleOS was more sane than whatever this is.
ahem, TempleOS generally tends to be considered a marvel of one-man engineering, not a cooky project. Despite Terry Davies' illness.
its so honest (3 matches), genuine (2 matches)
What in the AI slop?
What is the point of a "README" when no one is going to read that wall of slop.
As soon as I see the common AI fingerprints "No X, No Y", excessive use of commas, and extremely short sentences, it is likely that the author hasn't read the document and it now becomes a DONTREADME.
I appreciate the attempt to hide the AI slop style of the documentation, but it still very difficult to read and understand.
[flagged]