Michael Martinez :verified: on Nostr: npub1nfl23…d7t3d It's been a long time since I tried printing a file that only used ...
npub1nfl23e02pugcg2mltgjh4v3t3gps7ye3vc75epdw6klztnq5ms4qad7t3d (npub1nfl…7t3d) It's been a long time since I tried printing a file that only used NL as a terminator. The results were not good. Hopefully the printer drivers have all been updated.
It also mattered with CRT displays on multiuser systems. Maybe the drivers could be updated to no longer require CRLF.
But what do you do with the millions of legacy applications that essentially hardcode CRLF into their printing and display routines because that was what the hardware expected?
Will all that code have to be recompiled?
I can see updating printer and display drivers to handle NL = CRLF but really these kinds of proposals remind me of the advice to "minify" all the CSS and Javascript code to "speed up Web pages".
Minification doesn't do squat. But combining dozens or hundreds of external scripts into 1 file or embedding all that code in the main HTML document - THAT's a smart thing.
Google might not have invented QUIC (now HTTP/2) if developers had combined all their code in the first place.
Instead, we're now debating the supposed cost of retaining CRLF in the name of saving miniscule amounts of space.
Never mind just how much storage space on a 1+ terabyte drive is wasted for a simple 10K file.
It also mattered with CRT displays on multiuser systems. Maybe the drivers could be updated to no longer require CRLF.
But what do you do with the millions of legacy applications that essentially hardcode CRLF into their printing and display routines because that was what the hardware expected?
Will all that code have to be recompiled?
I can see updating printer and display drivers to handle NL = CRLF but really these kinds of proposals remind me of the advice to "minify" all the CSS and Javascript code to "speed up Web pages".
Minification doesn't do squat. But combining dozens or hundreds of external scripts into 1 file or embedding all that code in the main HTML document - THAT's a smart thing.
Google might not have invented QUIC (now HTTP/2) if developers had combined all their code in the first place.
Instead, we're now debating the supposed cost of retaining CRLF in the name of saving miniscule amounts of space.
Never mind just how much storage space on a 1+ terabyte drive is wasted for a simple 10K file.