I don't believe that is a bad reason for trying something. Committing resources to using ghost in a mission critical environment would be demonstrably silly - however being well informed of the tools available to you and their suitability to purpose is just good sense.
I don't disagree. I think the greater point here is that many people are irrationally choosing to switch to Ghost because "it's better" without really know why it is better. "Because it's not PHP" is the most irrational response I've ever read....
Good marketing showing how to solve problems most perceive they have...
I regret putting that in my original comment because I believe people take that to mean that I am PHP "hating" (I don't know what that even means). I set the record straight in another comment here: https://news.ycombinator.com/item?id=6547794 .
I use PHP extensively and think it has come a hell of a long way over the last couple of years. My meaning with the orignal point of "avoiding PHP" was more in the spirit of platform considerations.
You may, for whatever reason, not want to include PHP as part of your system architecture. By being written in JS, Ghost offers an alternative in terms of platform (where something like Drupal, or Dropplets would not).
The problem I have is why on earth is this an important feature set?
> You may, for whatever reason, not want to include PHP as part of your system architecture.
But why? why? why? Why it does it matter if it's called PHP or JavaScript or GabeSpeek (made up). As long it works and it's maintainable, why on earth does this make any rational person's (not saying you specifically) list of features?
Operating in a larger infrastructure where various components are set in stone and/or not available to them? In a shared hosting esque environment (granted they almost all have PHP by default) it is not impossible to imagine a situation such as this.
