Thanks for the pointer. That said, I’d prefer to have effective URI parsing be part of the core libraries. Also, I’d been pondering using JRuby, so it was nice to find a simple example of how I could benefit from JRuby.

Nice point. I have not reported this to Ruby Core, because I did not know if this was the desired behavior or not. If the Ruby URI parser intends to be strict then it’s acting appropriately (and annoyingly)… That said, per your suggestion, I will report it.

Blogged about it: I had a hell of a time with this problem and, whether or not it is fixed in Ruby, there’s a decent chance that someone else will have the same problem. I’ve also got a workaround if someone wants to handle problematic URLs in Ruby and I’ll add that to the post.

I’m not sure whether or not Turbinado is dead. I haven’t had much time to work on it since I’ve been focused on bringing some production websites online (and Turbinado isn’t production ready yet). I’ve got a post with some reflections on Turbinado and Haskell 50% written, so finishing that should help me think through my future plans for both.