These look easy, but I don’t think they always are.
Think about CSV for example. Looks simple to create and parse. In reality these simple implementations will give you lot of headache when they don’t handle edge cases (escaping, linefeeds etc).
Think about CSV for example. Looks simple to create and parse. In reality these simple implementations will give you lot of headache when they don’t handle edge cases (escaping, linefeeds etc).
$ hd
^^^_
00000000 1e 1f 0a
00000003
$ sort -t "^_" -k 2,2n
a^_42
z^_5
n^_7
z5
n7
a42In the real world the entire spec is contained in its three word name.
In the end I think the simplicity was also a weakness. Because the spec is so minimal a programmer goes "Oh, I'll just write my own, no problem", where a more complex protocol would have necessitated finding some exisiting library instead. Whatever the author of that library did would become the defacto standard and there would be less incompatibility between files.