Re:CRLF is obsolete and should be abolished
by michaelmior on Sunday October 13, 2024 @04:58PM
(#41831535)
Ignoring established protocols doesn't make things simpler. It makes things vastly more complicated.
Let's absolutely fix new protocols (or new versions of existing protocols). But intentionally breaking existing protocols doesn't simplify anything.
Re:CRLF is obsolete and should be abolished
by nsnshsuejeb on Sunday October 13, 2024 @05:42PM
(#41831898)
Yes. We all know how to do this. You know that API version thingy. I agree to drop the carriage return when not needed but do it in future protocols.
Obviously IPv6 shows you need to be patient. Your great grandkids may see a useless carriage return!
Windows doesn't help here.
Re:CRLF is obsolete and should be abolished
by perching_aix on Sunday October 13, 2024 @06:00PM
(#41832062)
Versioning provides people with capability for change management, but won't perform it on their behalf. Who knew.
It's not satire and it's not just trying to make a point. It's trying to make things simpler. As he says, a lot of software will accept input without the CR already, even if it's supposed to be there. But we should change the standard over time so people in 2050 can stop writing code that's more complicated (by needing to eat CR) or inserts extra characters. And never mind the 2050 part, just do it today.