17 pointsby hevolveai3 hours ago14 comments
  • DougN7an hour ago
    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.
    • an hour ago
      undefined
  • tpoacher40 minutes ago
    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!

  • reactordevan hour ago
    "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.
  • Arshad-Talpuran hour ago
    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?
  • KaiserProan hour ago
    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?

    • mafzzzan hour ago
      He asked codex to build this. He does not even know what it means when people say the term OS
    • hevolveaian hour ago
      [flagged]
  • DennisAleynikov2 hours ago
    Curious about where this is most applicable
    • mafzzzan hour ago
      Nowhere.

      The guy that asked an agent to build this does not even know what an OS is

      • xnickban hour ago
        Can you estimate how much it'd cost to make? Having ^F'ed "Load-bearing" I determined it must have been Claude
    • hevolveai2 hours ago
      [flagged]
    • 2 hours ago
      undefined
  • villishan hour ago
    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.

    • tpoacheran hour ago
      ahem, TempleOS generally tends to be considered a marvel of one-man engineering, not a cooky project. Despite Terry Davies' illness.
  • mafzzzan hour ago
    Calling this shit an OS, is a logic jump that no computer science engineer would do. But hey, we're living AI slop times.
  • calvinmorrisonan hour ago
    its so honest (3 matches), genuine (2 matches)
  • matthewfcarlsonan hour ago
    What in the AI slop?
  • rvzan hour ago
    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.

  • nathan_comptonan hour ago
    I appreciate the attempt to hide the AI slop style of the documentation, but it still very difficult to read and understand.
  • hevolveai2 hours ago
    [flagged]
  • 3 hours ago
    undefined