<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>>> Pretty much, yes. A full compatibility layer would like affect<br>
>> performance big time and a less intrusive version is probably not worth<br>
>> anybody's time to write.<br>
><br>
><br>
> But D7 not will be a less intrusive version, this is the point.<br>
><br>
<br>
</div>"less intrusive version" was referring to the compatibility layer, not<br>
Drupal.<br>
<br>
Basically, we've had similar discussions for Drupal 4.7, 5, and 6 and<br>
all were hailed as the end of Drupal as we know it because nobody would<br>
be able to update their modules in time, etc yadayada. We probably have<br>
had this discussions for even earlier versions but luckily I've managed<br>
to forget them.<br>
<br>
Executive summary: Compatibility layer == bad.<br></blockquote></div></div><div><br>I agree, but it's bat too rewrite from scratch every time a lot of code, like Views or CCK or Panels.<br></div></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br>Could be nicer have at least a stable API or a *drupalX-compat" plugin with older API, but bright people surely know this things better of me :)<br><font color="#888888">
</font></div></div></blockquote><div><br><br>
So far, it has proven to be an acceptable price to pay for innovation. Yes, it
causes some pain, but if we fix the APIs between major releases, this
will be the start of the end for Drupal, since it will either get
bloated by a compatibility layer (more resources, slow, complexity,
...etc.), or Drupal will stagnate and no longer become a leading
content management platform/application.<br><br>Having said that, there is nothing stopping YOU (or others) from building a compatibility layers. Some people tried that from Drupal 4.6 to 4.7 after Form API was in core. We just don't want that to be in core.<br>
<br>Better focus on tools that would make migrating your modules easier/quicker (core, deadwood, documentation for converting from 6.x to 7.x, ...etc.)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><font color="#888888"><br>P.<br></font></div></div><div><div></div><div class="h5"><br clear="all"><br>-- <br>Paolo Mainardi<br><br>Vice Presidente Assoc.ILDN (<a href="http://www.ildn.net" target="_blank">http://www.ildn.net</a>)<br>
Blog: <a href="http://www.paolomainardi.com" target="_blank">http://www.paolomainardi.com</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.<br>
Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra<br>Simplicity is the ultimate sophistication. -- Leonardo da Vinci<br>