How I got stung by the Twitter gem and thread safety
TL;DR
If you use sferik's Twitter gem with multiple accounts in a rails app, or a ruby app that uses concurrency in some way, then you need to be using the thread safe configuration.
TL;DR
If you use sferik's Twitter gem with multiple accounts in a rails app, or a ruby app that uses concurrency in some way, then you need to be using the thread safe configuration.
If you're a ruby developer, plugging a gem into a project is second nature. Most projects now use bundler to manage gem dependencies and versions, as it is so effective at doing so. If you've been doing this for long enough, then you will have come across the pessimistic version constraint operator, at least unknowingly.
The very first gem I ever created was actually pretty good. Apart from one thing: when you installed it, it didn't install the dependencies (i.e. the other gems that it depended upon). This might seem like a pretty big oversight, and it was, but there's a good reason. I actually did specify the dependencies - I just did it in the wrong place.