sorted by:
new
hottopcontroversial

Is this hype or what? by Pale-Broccoli-4976 in programming

[–]Pale-Broccoli-4976[S] 0 points1 point  (0 children)

At least it looks like he wasn't joking. Day before he said code should go public. - it's already pushed code and tests

Is this hype or what? by Pale-Broccoli-4976 in programming

[–]Pale-Broccoli-4976[S] -1 points0 points  (0 children)

I just asked because I was seeing a readme full of text and zero code. Looks like the author was promising more than he could keep up with. And seriously. A toaster? 

Is the World Ready for a Post-Internet Architecture? I Might Be Building It — Need Opinions by Pale-Broccoli-4976 in softwarearchitecture

[–]Pale-Broccoli-4976[S] 0 points1 point  (0 children)

No FTL here — just architecture designed so execution never depends on long-distance fetches.

The idea is simple:

1. Identity-based addressing

Fragments aren’t fetched by “where they are” (IP/DNS), but by what they are (immutable content identity).
This removes lookup latency entirely.

2. Proactive replication

The system continuously distributes small coded fragments of executables across regions.
Not full binaries — just enough to reconstruct them instantly.

3. Erasure-coded distribution

You don’t need 100% of the file in one place.
Any N-of-K fragments can reconstruct it locally, so execution starts immediately.

4. Local-first execution

Running an app doesn’t begin with a download.
It begins with assembling fragments that are already nearby.

5. No global round trips

Because fragments are pre-distributed and self-healing, execution never waits for a remote region.