4 ms·
Drupal's a little strange in that every major release (Drupal 5,6,7,8) is incompatible with the previous major release, so all of the contributed modules need t
by jefflinwood 11y ago
Drupal's a little strange in that every major release (Drupal 5,6,7,8) is incompatible with the previous major release, so all of the contributed modules need to be rewritten or updated.
In practice, this means that if you are going to build a Drupal site, it may take several months to a year after the official release before everything's stable enough to build out a new site.
Drupal 8 should simplify things a lot, compared to Drupal 6/7, in that they are actively developing Drupal for developers who aren't Drupal developers. The question is whether that's enough to make Drupal a viable CMS/application platform going forward.
- cdnsteve 11y agoThis can't be ignored. If you want to build anything of significance then you are re-writing your entire app every couple years, or less depending on their cycle. Literally nothing between 7 to 8 works. You are starting over. This is not acceptable in the markets Acquia is going after (enterprise).
- jacquesm 11y agoWorse than that. By the time the module eco-system has finally caught up Drupal has already moved on. It's un-workable.
- Domenic_S 11y ago> Drupal's a little strange in that every major release (Drupal 5,6,7,8) is incompatible with the previous major release Is that really strange? Isn't that standard semver "major releases break backwards compatibility/api"?
- gchokov 11y agoit's quite bad from whatever angle you decide to look on it.