I don't know what made him change his mind today, but after his
keynote at railsconf eu I've mentioned to him that people today are
using Engines for something pretty similar to what he suggested in his
talk ("concern'izing" stuff to modules), just one level up in the
architecture (i.e. using plugins). He was amazed and said he liked
that idea.
I'm just happy that finally I can stop dealing with fud in
#rubyonrails and elsewhere about "david says engines are deprecated".
Oh, btw ... James, thank you for Engines ;)
On 26.11.2008, at 17:49, James Adam wrote:
I believe David has discovered that he has a personal usecase for
them, essentially. As with most things that make it into Rails, one
of the contributors needs to personally need it for it to really be
considered :)
James
On 26 Nov 2008, at 16:39, Andrew Roth wrote:
I'm happy to see this but I am curious. Why did the rails team
change their minds?
On Wed, Nov 26, 2008 at 10:15 AM, Tekin Suleyman
<[EMAIL PROTECTED]> wrote:
http://github.com/rails/rails/commit/63d8f56774dcb1ea601928c3eb6c119d359fae10
Tekin Suleyman
Freelance Ruby on Rails Developer
+44 (0) 7968 355 460
http://tekin.co.uk
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
_______________________________________________
Engine-Developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
