andrius4669
Joined 12 years ago
Karma
205
Submissions
50
Member since
Oct 20
Joined 12 years ago
this rabbit hole goes deep...
some implementations carry the same "uncomparable" logic when checking for unique constraints, while others drop the ball here.
programming language wise, it's kinda like null pointer or float NaN, both of which are also occasionally complained about, eg. indexing maps by float values can do bogus things in case of NaNs.
edit: clarified some things
that exists, see https://en.wikipedia.org/wiki/Rich_Communication_Services
Just shows how easy it is to be wrong by being lazy with http parsing.
So while usability is pretty similar, they're pretty different underneath.