You know I love you, Earl, but just as a counter argument to all of these pieces of core that can be replaced by Views: in my experience, Views is significantly less efficient at doing most of those things.
I do admit and agree, that Views would replace a ton of core code, just as you write. And that a huge amount of flexibility would be gained, as well. I'm kind of obsessive about having fast, lightweight core code so that I can still build a very fast site without throwing lots of hardware at it. So, is there a way to incorporate Views in core, but avoid using its code in a specialized application built upon Drupal (except for perhaps rarely loaded pages, like user admin)? I can wish for the moon, can't I? :-) On Wed, Aug 12, 2009 at 12:04 AM, Earl Miles<mer...@logrus.com> wrote: > Cameron Eagans wrote: >> >> I think the argument of 'let's put views in core because it'll make >> setting up sites easier' is kind of a bad one in this case. Views is neither >> easy nor essential for -every- site out there. > > The argument for having Views in core is that Views would then power a whole > ton of core: > > tracker.module: Just a view. > blog.module: Just a view. > /node front page: Just a view. > /rss.xml: Just a view. > node content admin: Could be a view, with VBO. > user admin: Could be a view, with VBO. > recent comments block: Yep, a view. > recent blog posts block: Yep, a view. > active forum posts? Sho 'nuff. > > Having a bunch of this stuff be Views natively, instead of hardcoded queries > and whatnot, would be a big step closer to separating the API from the > Application, and the Application would become *much* more replaceable. And > tweakable. Because once it's a view, then on your site you can tweak it as > much as you can tweak any view. And that's rather a lot. >
