I’ve always hated case sensitivity. I know that at an ASCII level “variable” != “Variable” but is there really a reason to have a distinction between them?

[–] vithigar@lemmy.ca 22 points 2 weeks ago (1 children)

You stated the reason yourself. Those are different values and matching in a case-insensitive manner is more work under the hood.

[–] ramble81@lemm.ee 5 points 2 weeks ago (3 children)

We do plenty of stuff for human consumption. Computers work for us, not the other way around. Insensitivity should be the default. It’s okay to give options. I’m not saying take that away.

[–] WordBox@lemmy.world 5 points 2 weeks ago

Humans have to make it do the work. And that's how Mr; DROP TABLE makes his money.

[–] lengau@midwest.social 4 points 2 weeks ago* (last edited 2 weeks ago)

✋ Case insensitive filesystem
👉 Case insensitive file sorting

[–] calcopiritus@lemmy.world 2 points 2 weeks ago

For some reason we decided that a lot of formats written by computers and read by computers would use ASCII encoding instead of raw data.

Making a json or XML deserializer case insensitive would just make it slower for almost 0 benefit.

load more comments (4 replies)