No technical limits were hit. They have nearly the same feature set.
Geocoder's api feels a little bit more modern Geokit (rails3 vs 2). Having read the code for both, Geocoder was cleaner and would be easier to tweak if necessary.
So really it's just a preference: they do the same thing.
We're a nearly-funded startup creating a social platform for local communities and neighborhoods.
* Web Dev Intern: Will be working on a Ruby on Rails web app with some civic-minded Harvard students. Some programming experience nice, but not required. We will help you learn as needed.
Mainly, I'm tired of using $.getJson, and I liked your on-server macro.
Also, how is the server going to watch references on the server and vice-versa?
Awesome. I've got it up and running. I've been looking for a solution for the client/server distinction for a while. How much have you thought about the implementation of that?
I bought a nice hat from http://www.kleinbottle.com/ and he sent me pictures of it being packaged up, so this sort of thing has been done before. I've no idea about patentability though.
I used it a lot before and I use it a lot now. It took a bit of getting used to, but I rather like the new design. I've found that I'm listening to a lot more new music, where before the redesign I just kept listening to the same stuff over and over.