Right. Like how any potential reader is familiar with the risks of sql injection which is why nothing has ever been hacked that way.
Or how any potential driver is familiar with seat belts which is why everybody wears them and nobody’s been thrown from a car since they were invented.
So we shouldn’t mark anything as unsafe then? And give no indication whatsoever?
The issue isn’t that the word “safe” doesn’t appear in safe variants, it’s that “unsafe” makes your intentions clear: “I know this is unsafe, but it’s fine because of X and Y”.
because the "unsafe" suffix conveys information to the reader, whereas `innherHTML` does not?
Any potential reader should be familiar with innerHTML.
Right. Like how any potential reader is familiar with the risks of sql injection which is why nothing has ever been hacked that way.
Or how any potential driver is familiar with seat belts which is why everybody wears them and nobody’s been thrown from a car since they were invented.
yes, and bugs shouldn't exist because everyone should be familiar with everything.
But if some are marked unsafe and others are not it gives a false sense of security if something is not marked unsafe.
So we shouldn’t mark anything as unsafe then? And give no indication whatsoever?
The issue isn’t that the word “safe” doesn’t appear in safe variants, it’s that “unsafe” makes your intentions clear: “I know this is unsafe, but it’s fine because of X and Y”.
Maybe we should add the word safe and consider everything else as unsafe
Like life, things should default to being safe. Unsafe, unexpected behaviours should be exception and thus require an exceptional name.
Legacy and backwards compatibility hampers this, but going forward…
Because then your linter won't be able to tell you when you're done migrating the calls that can be migrated.
Because sooner or later it'll be removed.
No because the web has to remain backwards compatible with older sites. This has always been the case.
And break millions of sites?