HN user
A couple of years ago, in Argentina, my country, some idiot representative tried to create an actual law to force everyone to use the last name of both parents in strict alphabetical order.... and in the next generation, choose 2 out of 4 in strict alphabetical order, and in 10 generations everyone would have a couple of last names like aaaa aaab
I don't like using the body. GET's are easily shareable, bookmarkeable, etc, (even editable by humans). etc. thans to query strings. I rather have a GET with better (shorter) serialization for parameters and a standarized max-length of 16k or something like that.
Honestly, a port to a modern architecture, with more standard looking characters (like using # for comments instead of ~ and \n for newline instead of ! ) would be pretty interesting... It's amazing what that people used to be able to do with such limitations. 2k! I can barely make a CRUD app fit in 2G
So, paraphrasing:
Any sufficiently complicated Ruby program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Java