You would be surprised how many people are simply splitting the string on commas instead of using an actual ascii parser. Especially for one off scripts, like churning through a csv full of passwords.
CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.
Excel mangles everthing…
I work with a lot of EANs and every CSV import into Excel means I have to pay extra attention to the EAN field, because Excel likes to think for me, and thinks that the scientific notation would be very helpful for me… It’s not! 8.72E+12 is useless to me, Excel!!!
And don’t get me started on FEB-01.
Fuck Excel’s CSV handing. It differs by locale, silently. Imagine the thousands of people every year who patiently wait to import a multi-megabyte CSV from some instrument only to see garbage because their language uses the decimal comma and semicolon separator.
yeah unless you’re dealing with some steaming pile of vibe-coded shit this is a dumb as fuck idea.
(have seen people who don’t know how to appropriately use an LLM just let it wholly reimplement standards, read it over, and then say “oh wow that works great!” smh…)
of course there’s always been terrible code. people used to and still do reinvent the wheel all the time, even without the help of a robot.
trust me i’m one of the last people to shit on LLMs unnecessarily. the tools coming out nowadays are the bees knees. i think vibe coding is fucking awesome and most people’s premonitions against it are things that, similar to the premise, have just always been true - most of the “evil” of vibe coding can be dealt with easily by being a not shit engineer in the first place.
plus, not every problem needs to be a software development problem through and through. sometimes you just need a webui or an api to browse a dataset, for example - it’s not opsec critical and you need it now. that’s okay. the moral police won’t come to your house and arrest you for vibe coding.
CSV has standard escape sequences. This is pointless
See RFC-4180:
https://datatracker.ietf.org/doc/html/rfc4180
Then add escape sequence to your password!
Might as well just make a working regex and call it a password
You would be surprised how many people are simply splitting the string on commas instead of using an actual ascii parser. Especially for one off scripts, like churning through a csv full of passwords.
That standard won’t stop me because I can’t read!
CSV existed for over 30 years before RFC 4180. Excel, and countless other tools, have their own incompatible variants. Excel in particular is infamous for mangling separators when exporting to CSV.
Excel mangles everthing…
I work with a lot of EANs and every CSV import into Excel means I have to pay extra attention to the EAN field, because Excel likes to think for me, and thinks that the scientific notation would be very helpful for me… It’s not! 8.72E+12 is useless to me, Excel!!!
And don’t get me started on FEB-01.
I just fuckin’ hate Excel.
Fuck Excel’s CSV handing. It differs by locale, silently. Imagine the thousands of people every year who patiently wait to import a multi-megabyte CSV from some instrument only to see garbage because their language uses the decimal comma and semicolon separator.
I think semicolon separated files should be named SSV
yeah unless you’re dealing with some steaming pile of vibe-coded shit this is a dumb as fuck idea.
(have seen people who don’t know how to appropriately use an LLM just let it wholly reimplement standards, read it over, and then say “oh wow that works great!” smh…)
There was terrible code to long before LLMs, where do you think they got theirs from?
of course there’s always been terrible code. people used to and still do reinvent the wheel all the time, even without the help of a robot.
trust me i’m one of the last people to shit on LLMs unnecessarily. the tools coming out nowadays are the bees knees. i think vibe coding is fucking awesome and most people’s premonitions against it are things that, similar to the premise, have just always been true - most of the “evil” of vibe coding can be dealt with easily by being a not shit engineer in the first place.
plus, not every problem needs to be a software development problem through and through. sometimes you just need a webui or an api to browse a dataset, for example - it’s not opsec critical and you need it now. that’s okay. the moral police won’t come to your house and arrest you for vibe coding.