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…
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…
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…
So, paraphrasing: Any sufficiently complicated Ruby program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Java
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…
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…
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…
So, paraphrasing: Any sufficiently complicated Ruby program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Java