Drupal has features falling out of its butt. And where a feature doesn't exist, Drupal has highly generative systems that usually allow the clicking together of new features. We already have tons of stuff to make things "easy." Problem is, 'easy' doesn't scale.

Drupal isn't losing market share because its feature checklist isn't long enough. It's losing market share because its essential design makes it difficult to scale into complexity. Complexity slows down innovation, release cycles, and introduces a subtle upper bound on the interesting-ness of feasibly solveable problems.

So, if you really want to help out Drupal, don't think about features. Don't even think about "making it easy." Think about reducing complexity.

In this talk, I'll discuss where Drupal's complexity really is, how to think about it, why 'ease' is a deceptive goal and often the enemy, and how to think about writing code that reduces complexity.

Note: this talk blatantly borrows from Simple Made Easy. If you haven't already seen it, fix that. It's also a shorter, more example-filled reprise of my talk at Drupalcon Austin.