How to fix CSV: make it even more U+1F4A9 PILE OF POO
1–10 of 29 posts
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#2Technically editorialized title (since the original article just uses the emoji verbatim), but I think this is a net improvement.
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#3https://webcache.googleusercontent.com/search?q=cache:https:...
n.b. not worth your time. tl;dr: lets replace the comma with the poop emoji because commas occur in data.
There's already a solution to that (obviously). Best argument a contrarian could make is you "learn about unicode", by which they'd mean, the words "basic multilingual plane" are included at one point.
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#4Technically editorialized title (since the original article just uses the emoji verbatim), but I think this is a net improvement.
Emojis are disabled on HN (although in exceptional circumstances, staff have been known to edit them in)
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#5What if my data contains a new line? People focus on the comma then forget the newline is just as significant. That still needs to be escaped and we're right back where we started.
Meanwhile, RFC4180 takes less time to read than this entire article.
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#60x1d and 0x1e in the ascii standard exist for exactly this reason and don’t need more than one byte unlike this goofy thing.
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#7Not long ago there was also a post about "Unicode Separated Value"
https://github.com/sixarm/usv
https://news.ycombinator.com/item?id=39679378
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#8Perhaps naive, but we escape with \ everywhere else, so why not here?
If you're typing in CSV manually, escape with \
If you're exporting to CSV, the program already know which part is data and which part is the next cell, so again the program can escape with \
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#9Not long ago there was also a post about "Unicode Separated Value" https://github.com/sixarm/usv https://news.ycombinator.com/item?id=39679378
I was sure that's where this post was going to pivot to. The characters are right there!
Re: How to fix CSV: make it even more U+1F4A9 PILE OF POO
#10Not long ago there was also a post about "Unicode Separated Value" https://github.com/sixarm/usv https://news.ycombinator.com/item?id=39679378
Meant to link to this! Thanks, will update.