2 ms·
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?) b
by 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 agoNewer Rails has ActiveJob: https://github.com/rails/rails/tree/master/activejob https://github.com/rails/rails/tree/master/activejob