Login
You're viewing the functional.cafe public feed.
  • Nov 19, 2026, 4:15 PM

    @neauoire @yosh @m3tti CSV's handling of commas is very much a Microsoft solution of "Okay, well, commas in quoted strings won't....okay so quotes in quoted strings uh...."

    The Unix way would have been to say `,` `\,` and `\\` are the three magic strings for column separation, literal comma, and literal backslash. Done.

    💬 2🔄 0⭐ 1

Replies

  • Nov 19, 2026, 10:58 PM
    @spacehobo don't forget microsoft's decision to localise the decimal point in a data format (i.e. write 2,48 instead of 2.48), and then use a semicolon in a format called COMMA-separated values to work around the comma now being in use

    AND THEN decide to not build in any compatibility, so importing a US csv in a Dutch Excel install will just break as it's expecting a semicolon for the separator

    ugh this really gets me worked up

    @neauoire @m3tti @yosh
    💬 0🔄 1⭐ 0
  • Nov 20, 2026, 1:52 AM

    @spacehobo @neauoire @yosh @m3tti one of my chosen views to argue is that CSV and TSV should never have been necessary and not making it convenient to type the file, record, group, and unit separators that have existed in ASCII since essentially the beginning (and formalized in '73) is one of the great crimes of computing.

    💬 2🔄 1⭐ 0
  • 💬 1🔄 0⭐ 0
  • Nov 20, 2026, 10:07 AM

    @m3tti @LilFluff @neauoire @yosh You are asking the question answered by the post you are replying to. The crime is not that we should have sucked it up and used these separators on ASR37s, but rather that the computing hardware and interfaces should have made those symbols more accessible to users.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0