3 ms·

Think of all the coworkers you've ever had and see if you can imagine them writing RFCs and debating back and forth and revising them? I have worked at a lot o

Think of all the coworkers you've ever had and see if you can imagine them writing RFCs and debating back and forth and revising them? I have worked at a lot of companies and I find the kind of people who can or are willing and able to do that is decreasing. It's nearly zero today. If the Internet was invented today, it would work only for the happy path and fail with a million different error modes, each handled differently depending on the specific implementation. And you know what? People would accept it's unreliability probably, the way we accepted the 'all computers crash' from the DOS era till about NT 40. Everybody knew that computers just crash like that. :shrug: Today ChatGPT makes up facts and gets things wrong. But it's OK cos it's newer than Google, or printed books.

satvikpendem 4y ago
I sometimes participate in the Rust RFCs, so yes, I can imagine them writing RFCs and debating back and forth, which they do daily. Again you're focusing on coworkers and teams here and there at various companies, not in the best of the best who are the ones who built the internet and who would build it today. They are not average developers like one might normally work with, as I said, they are 0.0...1%.
kortilla 4y ago
> If the Internet was invented today, it would work only for the happy path and fail with a million different error modes, each handled differently depending on the specific implementation. This is exactly how the internet works today and you just don’t see it. Try using source routing in your IP packets and see how far it gets. BGP implementations had to carry a “work with Cisco’s bug” flag for decades. Send some >1500 MTU packets across the world with varying paths and see how fragmentation and assembly is inconsistent across operators and implementations. RFCs are loaded with errata, they skimp on critical details, and have bullshit “design by committee” features that never panned out. They aren’t special.

satvikpendem 4y ago

I sometimes participate in the Rust RFCs, so yes, I can imagine them writing RFCs and debating back and forth, which they do daily. Again you're focusing on coworkers and teams here and there at various companies, not in the best of the best who are the ones who built the internet and who would build it today. They are not average developers like one might normally work with, as I said, they are 0.0...1%.

kortilla 4y ago

> If the Internet was invented today, it would work only for the happy path and fail with a million different error modes, each handled differently depending on the specific implementation. This is exactly how the internet works today and you just don’t see it. Try using source routing in your IP packets and see how far it gets. BGP implementations had to carry a “work with Cisco’s bug” flag for decades. Send some >1500 MTU packets across the world with varying paths and see how fragmentation and assembly is inconsistent across operators and implementations. RFCs are loaded with errata, they skimp on critical details, and have bullshit “design by committee” features that never panned out. They aren’t special.