3 ms·

Here's the real issue. WordPress is more than a blog. Ghost is only attacking the blogging aspect of WordPress. The rich themes and plugins ecosystem of WordPre

Here's the real issue. WordPress is more than a blog. Ghost is only attacking the blogging aspect of WordPress. The rich themes and plugins ecosystem of WordPress cannot be matched no matter WHAT anyone thinks. Because of this, WordPress is widely used to develop all kinds of sites. Hell there's a company in my area (sadly I worked there years ago) who literally manages 200+ local businesses sites and they're all powered by WordPress. I'd say 1 or 2 of them are actually blog having sites. The rest are just "I want to be able to edit this section of content myself" sites. WordPress makes it insanely easy to build a site for a client or even anyone who's vaguely familiar with web development. Go get a cheap shared hosting account, click that 1 click WP install button, login to your new site, search for a theme you like, install it in a click, make a few minor tweaks, find some plugins that do stuff you like, install them in a click. Done. Until people realize this, there's no "taking on WordPress".

nhangen 11y ago
definitely. Not to mention WP's capability as an application platform. There are more PHP devs than node devs, and Ghost's adoption probably reflects that.
notNow 11y ago
I think that the whole ecosystem piggybacking on WP can be matched if not surpassed. There's nothing deficient or lacking in the technologies used in a Node stack to pull this off. We have npm already to cover the plugins functionality and on the front end it's a framework-a-palooza with libraries and themes popping every other hour. So, it can be done and I believe it can be easier and simpler whether for the end user or the developer as developing for WP is not really a walk in the park and there's a lot of gotchas and magic involved in this daunting process.
- Killswitch 11y ago
  The issue there is that the ecosystem is full of "I'd rather just install a plugin and be done" types. Nobody wants to recreate popular WordPress plugins to work in a NodeJS replacement. "Why would I recreate this in NodeJS where nobody uses it, when I can just use WordPress?"

nhangen 11y ago

definitely. Not to mention WP's capability as an application platform. There are more PHP devs than node devs, and Ghost's adoption probably reflects that.

notNow 11y ago

I think that the whole ecosystem piggybacking on WP can be matched if not surpassed. There's nothing deficient or lacking in the technologies used in a Node stack to pull this off. We have npm already to cover the plugins functionality and on the front end it's a framework-a-palooza with libraries and themes popping every other hour. So, it can be done and I believe it can be easier and simpler whether for the end user or the developer as developing for WP is not really a walk in the park and there's a lot of gotchas and magic involved in this daunting process.

Killswitch 11y ago
The issue there is that the ecosystem is full of "I'd rather just install a plugin and be done" types. Nobody wants to recreate popular WordPress plugins to work in a NodeJS replacement. "Why would I recreate this in NodeJS where nobody uses it, when I can just use WordPress?"