The fact that Windows fonts still default to displaying backslashes as yen-marks has been a perennial annoyance for me. A conversation about it today provided a wonderful illustration of just how irritating this can be.
Here is what I saw:
Here is what someone else saw:
This is just a humorous example of technology gone stupid, but it can be a very real disaster in source code (escapes are suddenly uncertain) and quite a few pieces of small business software (and even modern websites right now) have ridiculous output problems where a price is listed as “\50,000” — which isn’t such a big deal until you have a grid with invisible borders and see something that suddenly looks like a pricing equation instead of a statement of price: “500,000pc \ 50,000” Oops!
KILL THIS WITH FIRE WHEREVER YOU FIND IT.
I was talking with a friend of mine yesterday about how UUID v2 seems to have evaporated. We looked into things further and found its not actually included in RFC 4122! One thing led to another and I wound up writing an example project that is yet another UUID generator/utility in Erlang — but this time it actually has duplicate v1 and v2 detection/correction and implements as close to what I can find is defined as UUID version 2 values.
As there are already plenty of UUID projects around I focused on making this one as readable as I possibly could — to include exported documentation, in-source documentation, obvious variable names, full typespecs, my silly little “pure” notation, blatantly obvious bitstring syntax, and the obligatory github presence.
Hopefully some folks newish to Erlang will come along and explain to me what confuses them about that code, the process of writing it, the documentation conventions, etc. so that I can become a better literate programmer. Of course, since the last thing the world needs is another UUID implementation I suppose I would have had better luck with something at least peripherally related to the web. (>.<)