💾 Archived View for rawtext.club › ~sloum › geminilist › 000948.gmi captured on 2020-09-24 at 02:13:33. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
solderpunk solderpunk at SDF.ORG
Thu May 21 22:13:28 BST 2020
- - - - - - - - - - - - - - - - - - -
On Thu, May 21, 2020 at 04:54:47PM -0400, Sean Conner wrote:
Please, *please*, *PLEASE* do not let this disuade you from making most
clients out of spec. We have had to suffer terrible things because of this
thinking (like Makefiles and tabs---"when I realized my mistake, there were
already 10 people using it").
Point taken.
Specifying CR or CRLF but not LF would require the minimum amount of
rework, but it would be hard to justify this by anything other than
laziness.
And bizareness. The last time I worked on any systems that used only CR
was back in the 80s. Today everybody uses either CRLF (Windows) or LF
(Linux, Mac OS-X, whatever remaining bits of Unix are still around).
Yep, as stated, this should have been "LR or CRLF". Speccing that wouldrequire minimal changes to servers (which could just serve filesverbatim and assume nobody is generating CR-only files in this day andage), and clients (most of which could handle these two with either notrouble or minimal trouble).
But doesn't just picking two out of the three seem lazy? Or is thatjust me? Is it okay in 2020 to just write bare CR out of existence?
We basically need to choose between forcing server authors to normalise
all endings to CRLF or forcing client authors to recgonise LF (even
though it'll probably never be seen in the wild).
Would that be only for text/gemini? Or all of the text/* formats?
Ugh. Let me think...
Cheers,Solderpunk