Every few years, Drupal violates one of the industry's most sacred rules: don't break your APIs.
The next version of the popular open source content management system – Drupal 7 – will do just that. And more. It will offer a redesigned user interface that targets – gasp! – non-technical users. It will hide features that devs know and love.
Also in the works: Drupal Gardens, for hosting sites built with Drupal 7. It's analygous to Wordpress.com, and it's set to enter public beta "very shortly".
Such changes come at a critical juncture for Drupal. They're intended to help increase uptake among content creators – those outside Drupal's core audience of open sourcers.
This has been Drupal policy all along. They are concerned about the upgrade path, but have always said they reserve the right to break the API with major version upgrades and, in my experience, always have.
Why? Because they don't want "backward compatibility" to hamstring them which has some pretty bad effects of its own. I cite the example of Internet Explorer ;-)
1:41 am on Jul 23, 2010 (gmt 0)
No arguments from me! I merely posted the news. :)
2:40 am on Jul 23, 2010 (gmt 0)
Yeah, excuse my manners. Thanks for posting that - it's actually a good article and there is some interesting news in there. I just think it's funny that they lead with the API thing, which isn't exactly "news". I guess it's like the Vanity Fair fluff personality article that says "Tangor isn't your average WebmasterWorld member blah blah blah" so they can circle back to it for the last line.
I've tested Drupal 7 and generally like it, but think it's sort of a stopgap version (like Drupal 5). It's more like laying the groundwork for usability and media handling upgrades in Drupal 8... I think. I never upgraded to Drupal 5 though, but I'll upgrade sites to D7... once all the modules are converted a year from now ;-) That's the really killer of the API changes.