4 ms·
> That means they're not using it since they don't have to deal with spaces as spaces vs as separators The end-user isn't consciously using it. The software th
by skissane 3y ago
> That means they're not using it since they don't have to deal with spaces as spaces vs as separators
The end-user isn't consciously using it. The software they are using is.
We are talking here about programmer-visible reality, not end-user-visible reality. Those two realities don't have to be the same, as in the "replace spaces with underscores and vice versa" idea.
> So how do you differentiate between a user inserting a space and a user inserting a literal _ in a file name?
Underscores are rarely used by non-technical users. It isn't a standard punctuation mark. Back when people used typewriters, the average person was familiar with using them to underline things, but nowadays, the majority of the population are too young to have ever used one. I doubt many non-technical users would even notice if underscores in file names were (from their perspective) automatically converted to spaces, since they probably wouldn't put one in to begin with.
- eviks 3y agoI'm talking about the general reality (that you keep ignoring) and pointing out that it's much bigger than the programmer-visible one. For example, the "not many" non-tech users who would notice the broken unescaped underscores is a bigger group than all the programmers given how much bigger the base group is. You're just fine breaking their workflows just because a small group of professionals can't fix their APIs