To Drupal or not to Drupal

You do not have access to any projects.
in

I just read the constructive criticism about Drupal article To Drupal or not to Drupal, why we chose not to use Drupal for a photo shop. I must admit I'm on of those it points out at the end :

Never forget that you, as Drupal developer, have the conditions under wich your (future) sites are running, hardwired into your brain. Because after lots of Drupal development you start to think that the Drupal Way is The Only Way (this is a joke, people!).

This gave me another perspective and would make me consider other tools for my client needs but I still feel that way as soon as I get out of the boundaries of what tailor-suited solutions is already out there.

I'm assuming that the solution involved is proprietary, closed source and without a development community. Something the article didn't bring up is that tailor-suited solutions had all their extra fabric cut off and won't suit anything else and usually, just as people mensuration, vary along its lifetime and the suited solution might become the cursed solution or might require another solution which have another set of requirements, support, training, ...

I only went through a quarter of a huge book about software engineering but it seems that many concerns which it brought seem to apply on such a tool.

What I love about a free open sourced solution is that for whichever reason the developer needs would vary from the community supporting it, you could always make a fork and create your own community. In lesser case scenarios, make core patches and the likes which I doubt a proprietary solution would allow at an affordable cost.