Уровень 0 · материалов: 3
В кластер включаются документы с критическим анализом технического состояния и управления Drupal, и исключаются любые материалы, не содержащие негативной оценки данной системы.
Общие признаки: архитектурные недостатки Drupal, проблемы управления проектом, технический долг, негативная оценка качества кода
Группа выше: Конкретные CMS и создание собственных
Смысл: The main idea is that Drupal suffered a systemic collapse in quality and governance due to poor project management, corporate conflicts of interest with Acquia, and a failure to prioritize core stability over superficial features, leading the author to advise against its use for new projects.
The author argues that Drupal is in a state of technical and organizational decay, characterized by an overwhelming bug backlog and a shift from community-led to corporate-driven development.
Смысл: The main idea is that Drupal 7's development was marred by poor planning and feature creep, leading to an unsustainable amount of technical debt that threatens the future of the project and the release of Drupal 8.
The author argues that Drupal is in a critical state due to massive technical debt and poor management in Drupal 7, requiring a radical core simplification to survive.
Смысл: The main idea is a critical evaluation of Drupal 6 from a developer's perspective, arguing that its architectural flaws, lack of OOP, and poor caching make it unsuitable for professionals who prioritize clean code and scalability, although it remains useful for rapid, basic deployment.
A developer expresses deep frustration with Drupal 6's architecture, caching, and lack of OOP, ultimately recommending Symfony as a superior alternative for professional development.