[development] Drupal as an API: where the value is ...

Ivan Sergio Borgonovo mail at webthatworks.it
Thu Mar 27 19:12:51 UTC 2008

On Thu, 27 Mar 2008 13:35:21 -0400
"Khalid Baheyeldin" <kb at 2bits.com> wrote:

> Agreed.
> If only that the modules in core allow a basic blog or site, and
> demonstrate how to use the API.

> We are not CakePHP, Qcodo or Django in PHP.

I didn't want to make comparisons but you stole my words. Since we
are at it Drupal is not Joomla, XOOM, Xaraya on the other side.

Making Drupal a self-sufficient application make the difference
between having specialised libraries and have a CMS RAD.

Still I'd like Drupal move more in the direction of Django rather
than on the other side.

Some months ago this topic came out with another face, and people
were discussing the importance of being a premier blog app.

Honestly even if I still think Drupal is the best on its category,
things like comments, blogs, forums comes in to the way more than
what they may help for many use case.
Drupal couldn't live without an out-of-the-box working blog, forum
etc... but I'd like to see these things getting more modularised in
their features so that a default install would be "slimmer" with
default setup.

Still if the process of modularising what Drupal offers will make it
lose some features in the process I think it will have a high cost in
user base.

So before stuff can be kicked out of core there should be such a nice
API that will make trivial to rebuild what's in core now and may find
a better place in contrib.

Then anyone that would like some "non trivial" stuff... will just go
a step further.

And maybe the actual blog/forum etc... implementation will just be
part of the API documentation to "demonstrate" how it works.

Ivan Sergio Borgonovo

More information about the development mailing list