<div class="gmail_quote">On Wed, Aug 12, 2009 at 1:34 PM, Earl Miles <span dir="ltr"><<a href="mailto:merlin@logrus.com">merlin@logrus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Jamie Holly wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yeah I agree we really need to keep Drupal lean. I wouldn't want to see the entire Views package integrated as-is. I wouldn't mind some of the functionality included <br>
</blockquote>
<br></div>
This one drives me crazy. There really isn't a 'some'. There is no Views lite. Stripping out functionality does not make Views lighter, it just makes it less useful, and that is ultimately harmful. The reason Views is useful is because it is flexible.<br>
<br>
The reason it seems like it is 'heavy' is because it's defining handlers to deal with a couple dozen core tables, hundreds of core fields, half a dozen different styles (table, unformatted, node view, rss, etc). It is replacing a LOT of core functionality. When it goes into core, a lot of core code just gets thrown away.<br>
<br>
Anyway, people who have this attitude are really saying they don't want Views in core. That's fine, but what that really means is that core doesn't get the benefit of Views functionality. It degrades the overall user experience and it creates a lot of dead code in core that mostly is never used because 90% (or more) of the people using Drupal install Views anyway. (Right now, statistically, views is on 60% of all reporting Drupal sites).</blockquote>
<div><br></div><div>Let's get real. Views should be in core because it really is at the core of what sets Drupal apart from other CMS frameworks. And at the same time it being in core would be part of a positive refactoring which would go a long way towards paying some of the code debt Drupal has. </div>
<div><br></div><div>Let's get real. Views in core: +1.</div><div><br></div><div>Victor Kane</div><div><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
Also, one day I may not be able to maintain Views. I don't want to sound like an asshole...but I am an asshole. Every one who doesn't want Views in core had better consider the day that I move on from my current position, and am no longer able to maintain Views more or less full time on someone else's dime. If it's not in core, it could just become another unmaintained contrib module. Core is maintained by a large community. Views is maintained 95% by me and 5% by a handfull of other people who've gotten into it enough to understand it.<br>
<br>
But also, and this is the real reason: Core would be *better* with Views in it. Views in core is actually part of the #smallcore ideal, IMO, because it lets us do a better job of reducing core to APIs and building the Application on top of it, rather than core being half framework and half application, like it is now.<br>
<br>
</blockquote></div><br>