I wonder how many rfcs are nonsense like this since there are thousands and thousands and no one reads them all.
RFC 1925: The Twelve Networking Truths (1996)
21–30 of 39 posts
Re: RFC 1925: The Twelve Networking Truths (1996)
#22I wonder how many rfcs are nonsense like this since there are thousands and thousands and no one reads them all.
Note the publishing date on that RFC.
Also (of course) there is a Wikipedia list of funny RFCs, many with a similar publish date: https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for...
Re: RFC 1925: The Twelve Networking Truths (1996)
#23Every old idea will be proposed again with a different name and a different presentation, regardless of whether it works. I'm old enough to have lived through this multiple times now :-(
What is there to be sad about retrying ideas? Maybe the reason they failed the first time is no longer true.
Because often they DIDN'T fail the first time. It's just that when the next batch of devs decided they needed something, they didn't bother learning from the previous generation, and instead re-did every mistake of the past 30 years, to finally "invent" the already-working approach that had been there for decades.
One example that springs to mind is GUI code. We've gone through 3 cycles of that so far (including the original).
Another is programming languages.
Re: RFC 1925: The Twelve Networking Truths (1996)
#24Every old idea will be proposed again with a different name and a different presentation, regardless of whether it works. I'm old enough to have lived through this multiple times now :-(
Said every old person since the beginning of sentience
Re: RFC 1925: The Twelve Networking Truths (1996)
#25I wonder how many rfcs are nonsense like this since there are thousands and thousands and no one reads them all.
Note the publishing date on that RFC. Also (of course) there is a Wikipedia list of funny RFCs, many with a similar publish date: https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for...
The first thing I have seen was the date, than I came back searching this comment...
Re: RFC 1925: The Twelve Networking Truths (1996)
#26> Internet Order of Old Farts
Chef’s kiss
Re: RFC 1925: The Twelve Networking Truths (1996)
#27Earlier quoted context omitted.
What is there to be sad about retrying ideas? Maybe the reason they failed the first time is no longer true.
Because often they DIDN'T fail the first time. It's just that when the next batch of devs decided they needed something, they didn't bother learning from the previous generation, and instead re-did every mistake of the past 30 years, to finally "invent" the already-working approach that had been there for decades. One example that springs to mind is GUI code. We've gone through 3 cycles of that so far (including the…
And biggest one is cloud.
We went from sending our code to run at mainframe owned by big corporation and leased monthy for a price to sending our code to big corporation to run at not-mainframe for a monthly price
Re: RFC 1925: The Twelve Networking Truths (1996)
#2813. It's always DNS.
DNS is nice, it's the only internet protocol that "just works" and doesn't need tuning with obscure Linux-only system parameters.
Maybe it's because I don't use bind.
Re: RFC 1925: The Twelve Networking Truths (1996)
#29I wonder how many rfcs are nonsense like this since there are thousands and thousands and no one reads them all.
If I haven’t posted this RFC to a new group I am working with, the collaboration is still new and we haven’t fully bonded. This RFC will be true and useful long after TCP is a historical relic.
Re: RFC 1925: The Twelve Networking Truths (1996)
#30Next time I see a terrible comedian I will wonder if they could have been inventing the internet instead. It's strange to read humour from an age when jokes didn't have to be pro level mind blowing to be funny though. Simpler times.