Let me first concur with André and Jorge. Your entitlement is unwarranted (literally, as in there is no warrant for this level of entitlement per the MIT license of both Bundler and Rails), and decreases the odds that anyone is going to donate time to address any of your issues as a matter of good faith.
Second, "the "split complex rails app into gems/engines" mantra that the Rails team has been pushing a couple years now". Not sure where you got this from. I'm not pushing this. I think it's generally a bad idea. Less bad if the sharing is just a few models, more bad if its controllers, and extra bad if views are included as well. So you're right: Dealing with bigger apps by splitting them into a bunch of engines is not well supported because it's not a use case or pattern that has much backing from Rails core. But the lovely thing is that this is open source! You get to see all the code, and if things aren't being fixed by the community at large, you can fix it yourself or pay someone else to do it for you. So please do that and come back with some PRs that the teams can consider. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
