3 ms·
I think the point of the original post is that Ruby can parse URL-like syntax (e.g., http://twitter.com/statuses/show/6592721580.json http://twitter.com/statuse
by stephencelis 17y ago
I think the point of the original post is that Ruby can parse URL-like syntax (e.g., http://twitter.com/statuses/show/6592721580.json http://twitter.com/statuses/show/6592721580.json) as code, no strings attached.
- sketerpot 17y agoThat sounds like it might be a little awkward to parse. I think I prefer the Lisp+PURI syntax, just because you can see where the URL begins and ends easily, and don't have to worry about how the syntax interacts with the rest of the language.
- stephencelis 17y agoOh, it's completely awkward, and completely fun. The point wasn't to create a new library to supplant others (if someone used this code in production, I think the joke would be on them), it's to have fun with what's possible in Ruby, and perhaps save a few characters in irb.