This terminology has never sat well with me. I haven't had the time really to articulate why. Allow me to explore my thoughts further.
I fully recognize that people need to use the right tool for the right job. But, this philosophy suggests Drupal is not the right tool for less ambitious digital experiences. What about sites for local non profits, web presence for a local restaurant without any digital staff, or local religious organizations that desire a straight forward way to communicate their mission to the world on a shoestring budget. Drupal was built on the backs of people creating websites for causes they supported. I would argue that some of these sites don't need or even care about something ambitious. My philosophy of Drupal and its community is one of inclusiveness. It should be a platform for all, not just the ambitious.
Let's explore this from a business value perspective. Enterprises desire and have the capability to support an ambitious digital experience. Drupal presents a substantial value proposition for companies that can manage the complexity involved. Full time staff may help nurture the ongoing needs of a Drupal system, evolve the application to the organizations needs, create a robust and supporting cloud-based infrastructure, and, to summarize, truly leverage the ambitious nature of Drupal. Many organizations are drastically less ambitious with their goals. How does Drupal serve them?
Let's explore this from a technology perspective. Many developers would argue, "hey, Drupal ships with all of these cool tools. Why would anyone not want this amazing technology?" Fair point. First, let's acknowledge that these cool tools come at a cost. Drupal is overtly complex to use because it's aim is to provide the tools needed to support ambitious digital experiences. As technologists, we should be familiar with the YAGNI principle (you ain't gonna need it), which more closely aligns with a "small Drupal core" philosophy. This is not something that, as a community, we have agreed upon. Instead, we have a very large core Drupal system, a robust set of features, many dependent PHP and JS libaries, and technology spanning site building, development, theming, devops, security, and so much more. We've tackled ambitious goals. But, the end result is a steep learning curve, a significant amount of technical debt, and a system that requires our stakeholders to be highly informed to be effective. Is this truly needed for simple sites?