True. However, working within our architecture and finding a good fit for most use cases was what trumped all else for the feature launch. I like the library we chose and hope it gains traction as a pure ruby highlighting lib but if for some reason it doesn't fit our users needs, we can certainly find a way to accommodate them.
Truth is, I picked CodeRay for two reasons. It's fast and it's pure ruby. Pygments is great and I spent some time on a version that used it but CodeRay just fits better within our app. It's pure ruby, supports most languages I thought we should start with, it's extensible and has a roadmap for things that I could see our users asking for.
I just made this same move a couple months ago. I got a job out here. So my girlfriend and I sold most everything, including my car and drove over with 2 cats. While I can't recommend driving across the country with two cats, I can say that I am glad we got rid of everything. Purging yourself of all your things and starting over is an interesting experience. I have never been one to acquire lots of stuff but I had my share. Getting rid of it all helps you realize how small you can live and still be happy.
Am I the only one who reads posts like this and wonders why people make merging/pushing/pulling with Git so complicated? It's really not that hard. Sure there are plenty of esoteric and strange things you can do with Git but I have seen devs go from zero knowledge to using the basics in no time. Some never have to go beyond the add, commit, push, pull and merge commands (with their respective switches) and work quite happily. Sure they aren't Git experts by any means but they are able to get their work done and the tool is just as transparent to their workflow as any other SCM tool.
Depending on the language, usually...
Google (of course). Then apidock.com (for ruby / rails) pretty much the best doc site for either in my opinion.
For Rails I have found that just browsing the source/comments on github is the best source for figuring out really tricky issues. I stay logged in to IRC but most of the time never feel like bothering anyone. I kind of enjoy figuring things out for myself, even if it's a trivial problem I still get satisfaction from solving things on my own.
At my company we haven't found a way to charge more, especially with clients that have internal apps that will only work with IE6. What we have been doing is itemizing any hourly work spent on IE6 optimization (hacks). So, at least for clients with multiple projects in the works, it make them think twice about requesting IE6 support on their next project.