Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sorry, this still sounds like architecture astronautics to me. You have an intuition that things could maybe be simpler, which is not a bad place to start, but then you have to ground it in the actual reality.

> You're thinking of it from an IP perspective where there are individual devices in some chain

What do you plan to replace the individual devices with?

Looking at the traceroute in question, something I'd suggest you do for your own, I see one router owned by me, 6 by my ISP, 2 at an interchange, 5 for a backbone, a number of intermediate ones of mysterious ownership, and finally one owned by Amazon, presumably with a bunch of other Amazon hops that are hidden from me.

These are physical devices connected by physical links (wires, cables, fiber). Wires that people installed. Wires that break. Connected to devices that break. What in your proposed grand vision will happen there? Please start with the happy path and then give detail on the failure cases.

A similar problem applies in Amazon. The abstraction they hand you is pretty convenient. But that abstraction is made out of many millions of devices connected up in cunning ways.

Linux can connect two processes because the kernel has total control over a modest number of CPUs and RAM. That just doesn't compare to literal billions of interconnected devices with no central control. It's like saying that because your dad knows your mom's name and how to reach her, he should be able to do the same thing for everybody in his country.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: