Re:Rescuing Resque again (2015)
by steveklabnik on Friday January 15, 2016 @02:51PM
(#10911639)
Sidekiq has a lot of attention amongst new developers, but has at least an order of magnitude less users, at least, if gem downloads are something to go by. So from my standpoint, those people deserve bugfixes, and "throw away what works just to transition to something new" isn't really a great response.
Threading vs process-based jobs is a tradeoff. Threads are not universally better.
As of today, Resque has 6,308,611 downloads. Sidekiq has 5,669,265 downloads. Can you explain why you think "order of magnitude"?
Re:Rescuing Resque again (2015)
by steveklabnik on Saturday January 16, 2016 @09:44AM
(#10915366)
Hey Mike! Sorry, I 1) mis-read that number, 2) when we used to release more often, the download counts for latest versions used to be 10x yours. I don't think that's true at this point. I will update that cache in my brain and not say this again, I apologize.
No worries, I just wanted to make sure you didn't have access to super secret Ruby usage numbers that I didn't!
Re:Rescuing Resque again (2015)
by steveklabnik on Saturday January 16, 2016 @10:09AM
(#10915434)
I wish. :)
Something I've wondered for awhile: what are the benefits of continuing Resque development, rather than focusing on making the migration path to Sidekiq as painless as possible? Put another way, what do you hear from users of Resque (like Shopify, as you mentioned in another comment) as the reason that they don't want to migrate off of it?
I was curious about this way back in 2012 when you announced work on Resque 2.0, and I had already made the switch to Sidekiq. I thought there must be a good reason to keep working on it, but I wasn't sure what it was, and I'm still not sure, so I figured I'd just ask.