4 ms·

I have to be honest here. My initial thought when reading this a couple of weeks back was that some things are better left to dead. Resque has been an example

I have to be honest here. My initial thought when reading this a couple of weeks back was that some things are better left to dead. Resque has been an example of how not to run an open source project for a while now. (3+ years). We were working with Resque for a long while and had a lot of issues with performance. Sidekiq is awesome and it's being well managed and releases are frequent. But, after thinking about it, I think that Resque has it's place in the community, I definitely think that more than a single project doing this task is needed. Many people are already familiar with Resque and trust it, those people should be taken care of. I wish everyone involved a lot of luck with it.

sanderjd 11y ago
This is another good answer to the question[0] I just posed to Steve. You're right that competition is generally good. On the other hand, it would (arguably?) be much more "Rails-y" to have a single conventional solution that works well and gets a lot of eyeballs. Neither Resque nor Sidekiq are that thing though. It has always struck me as a bit odd that Rails outsources the decision on this component, which nearly every Rails project needs. I think previously it was probably to avoid an external dependency (on Redis), but perhaps that could be reconsidered now that >5.0 has eschewed that avoidance. Having said all that, one of the things that is most exciting to me about Elixir/Phoenix is that this sort of thing doesn't even come up, because a great and mature solution is built directly into the runtime. [0]: https://news.ycombinator.com/item?id=10911600 https://news.ycombinator.com/item?id=10911600
- steveklabnik 11y ago
  Newer Rails has ActiveJob: https://github.com/rails/rails/tree/master/activejob https://github.com/rails/rails/tree/master/activejob
steveklabnik 11y ago
Thanks! > Resque has been an example of how not to run an open source project > for a while now. (3+ years). Resque is the story of a gem that _everyone_ uses, yet nobody invests in. So the maintainers burn out, and burn out, and burn out. Chris, Terence, Me... trying not to do that again ;)
- avitzurel 11y ago
  The problem actually started before you guys came to the Resque :) I remember you commented on my open source project (Resque plugin), I was impressed with the reach of how deep you want to go with this. I agree with what you said 100%, everyone is using it and no one invests in it. That's why it's hard to maintain and that's why Sidekiq is "winning". Since money is a justified investment to any company for that project and it keeps the project going.

sanderjd 11y ago

This is another good answer to the question[0] I just posed to Steve. You're right that competition is generally good. On the other hand, it would (arguably?) be much more "Rails-y" to have a single conventional solution that works well and gets a lot of eyeballs. Neither Resque nor Sidekiq are that thing though. It has always struck me as a bit odd that Rails outsources the decision on this component, which nearly every Rails project needs. I think previously it was probably to avoid an external dependency (on Redis), but perhaps that could be reconsidered now that >5.0 has eschewed that avoidance. Having said all that, one of the things that is most exciting to me about Elixir/Phoenix is that this sort of thing doesn't even come up, because a great and mature solution is built directly into the runtime. [0]: https://news.ycombinator.com/item?id=10911600 https://news.ycombinator.com/item?id=10911600

steveklabnik 11y ago
Newer Rails has ActiveJob: https://github.com/rails/rails/tree/master/activejob https://github.com/rails/rails/tree/master/activejob

steveklabnik 11y ago

Thanks! > Resque has been an example of how not to run an open source project > for a while now. (3+ years). Resque is the story of a gem that _everyone_ uses, yet nobody invests in. So the maintainers burn out, and burn out, and burn out. Chris, Terence, Me... trying not to do that again ;)

avitzurel 11y ago
The problem actually started before you guys came to the Resque :) I remember you commented on my open source project (Resque plugin), I was impressed with the reach of how deep you want to go with this. I agree with what you said 100%, everyone is using it and no one invests in it. That's why it's hard to maintain and that's why Sidekiq is "winning". Since money is a justified investment to any company for that project and it keeps the project going.