3 ms·
It being included will have no performance overhead since it's only loaded if it's used. I'm personally for this idea, I've used DJ, Resque and Sidekiq, all in
by unfunco 12y ago
It being included will have no performance overhead since it's only loaded if it's used.
I'm personally for this idea, I've used DJ, Resque and Sidekiq, all in the same project (increasing load), and in that order; It would have been much nicer to have to only change the Gemfile when I made the switch.
Your comment, whilst a perfectly valid concern, reminds me of an article DHH posted: http://david.heinemeierhansson.com/2012/rails-is-omakase.html http://david.heinemeierhansson.com/2012/rails-is-omakase.htm...
- kalleth 12y agoPerformance wasn't my concern at all. Overcomplicating the rails 'core' is my concern. I'd much rather start from a lightweight 'base' which solves most of the common cases and pull in extras as required for what i'm working on. Rails should be a framework that allows you to layer extra functionality ontop of it.