"Of all the monsters that fill the nightmares of our folklore, none terrify more than werewolves, because they transform unexpectedly from the familiar into horrors. For these, one seeks bullets of silver that can magically lay them to rest.
The familiar software project, at least as seen by the nontechnical manager, has something of this character; it is usually innocent and straightforward, but is capable of becoming a monster of missed schedules, blown budgets, and flawed products. So we hear desperate cries for a silver bullet--something to make software costs drop as rapidly as computer hardware costs do.
But, as we look to the horizon of a decade hence, we see no silver bullet."
- Fred Brooks, from No Silver Bullet: Essence and Accidents of Software Engineering (circa 1987)
Peter Van Dijck mentions that a mysterious man by the name of "Mike" asserts on some mailing list that he "can think of at least 5 startups that were seriously hurt by using Drupal”. That hit close to home: I work for a startup that is using drupal. Is my startup in danger of failing? Clearly, the answer is yes. To quote Captain Obvious,
"Launching a web startup is inherently dangerous business; the success rate is depressing at best. The odds are that you will fail -- and fail miserably at that. People may even laugh at your startup for years to come."
Is my startup in danger because we are using Drupal? The answer is no. Unless me and the other developers didn't know how to work with drupal (and we certainly do). On the otherhand, there are about 100 other factors that might lead to us failing, all of which keep me up at night:
These factors are unchanging no matter what technology you use. Would these unnamed startups that allegedly failed on account of drupal succeeded had only they used RoR, Java, Plone, Coldfusion, or build something home grown?