Posted by boris mann on September 19, 2010 at 11:29pm
I don't think we can go "framework only". See Code Igniter for an example of this. Expression Engine just got rewritten in Code Igniter ... sort of. More people have heard of EE than have heard of Code Igniter.
I understand what you're thinking with regards an "official" distro + "framework". I think the main Drupal download needs to actually do this in one download - we need an EASY starting point that some people will go off and code for, and others will extend with modules.
My pain point is that no one seems even willing to engage on what default.profile should actually do out of the box. I've written about it here before - I think it should focus on multi-user, multi-role, multi-permission functionality out of the box (some might call this community although I would aim for less than that in core) - something that plays to Drupal's strengths.
The main problem with this is it starts with something that doesn't do anything out of the box. Drupal core should really be the product with maybe a Drupal Framework release much like there is a Pressflow release.
Remember that quick product iteration only works well if backward comparability exists. If there is a new version of Drupal every nine months that didn't work with the previous version's modules then developers would drop off or the community would branch.
In my opinion, it is better to build a large scale product that does everything and is rock solid and release it every few years.
Comments
Nope
I don't think we can go "framework only". See Code Igniter for an example of this. Expression Engine just got rewritten in Code Igniter ... sort of. More people have heard of EE than have heard of Code Igniter.
I understand what you're thinking with regards an "official" distro + "framework". I think the main Drupal download needs to actually do this in one download - we need an EASY starting point that some people will go off and code for, and others will extend with modules.
My pain point is that no one seems even willing to engage on what default.profile should actually do out of the box. I've written about it here before - I think it should focus on multi-user, multi-role, multi-permission functionality out of the box (some might call this community although I would aim for less than that in core) - something that plays to Drupal's strengths.
Depends
The main problem with this is it starts with something that doesn't do anything out of the box. Drupal core should really be the product with maybe a Drupal Framework release much like there is a Pressflow release.
Remember that quick product iteration only works well if backward comparability exists. If there is a new version of Drupal every nine months that didn't work with the previous version's modules then developers would drop off or the community would branch.
In my opinion, it is better to build a large scale product that does everything and is rock solid and release it every few years.