>I understand, but as a used, I really don’t give a damn.
Yeah, Because we already changed " to 69 behind their back, let's double down on correcting the 69 so it processes like "!
Let's engineer our dumb, close-minded O(n) string search and CSV parser to do some AI image recognition shit in O(2^n) to figure out when the fuck the "used" had the ` involuntarily changed to ' because MacOS or Wordpress decided it looks better.
That's brilliant engineering right there.
Satire aside, you realize that there is a cost of security and maintenance to over-engineer shit, it's just not just convenience, right?
Your specific bug with CSV is a developer bug. The place where you copied the incorrect CSV format should not have had such substitution enabled. On the Mac, developer can specify for each text view and text field what substitutions are allowed by default. Likewise in web, it is possible to specify which substitutions should be allowed for text areas.
So instead of blaming incompetent developers for their incorrect use of system features, thus ruining some very narrow cases, let's hold back any kind of text input and processing advancements, because you are unable to input some CSV properly.
That's brilliant engineering right there.
When my mother types on her computer, she just wants things to work. When she searches for something, she doesn't care if she typed the wrong incorrect Unicode character. That's the cases that need to be solved for users.
And it is only O(2ⁿ) algorithm if you naively look at text as an array of bytes. Time to, perhaps, broaden some horizons.
When you use your mom as a baseline, then do you think she would give a single fuck about how the " should look like? Does she zoom in the text with a magnifier glass to complain oh no they didn't change my " to 69, this doesn't look right, my os is shit?
Or she cares more when the shit she copy-and-pasted from some random website or your note to her to do something doesn't work because the site or the copy-paste process meddled with it?
PS: The joke is on the O(2^n) with AI Tensorflow, not on the "used." The "used" thing was 101% serious.
Yeah, Because we already changed " to 69 behind their back, let's double down on correcting the 69 so it processes like "!
Let's engineer our dumb, close-minded O(n) string search and CSV parser to do some AI image recognition shit in O(2^n) to figure out when the fuck the "used" had the ` involuntarily changed to ' because MacOS or Wordpress decided it looks better.
That's brilliant engineering right there.
Satire aside, you realize that there is a cost of security and maintenance to over-engineer shit, it's just not just convenience, right?