Hacker News Reader

Comment by coldtea | Hacker News Reader

>So Automattic, maker of the largest open source PHP CMS in the world has thrown out PHP in favor of node.js for their own site.

No, they kept PHP for the backend, and created a new front-end with node and JS. And that's just for the admin pages.

>If they're leading by example, we should ditch WordPress.org and PHP in favor of node.js web apps and frameworks too, since it's the way of the future?

Perhaps. Do you expect Automattic to tell you what your stack should be?

Besides, if node/Js is the "way of the future" then there's no need to ditch "wordPress.org" since it has already embraced that future.

View on HN

>Besides, if node/Js is the "way of the future" then there's no need to ditch "wordPress.org" since it has already embraced that future.

How?

Through the availability of said announced open source node/js admin panel + client that works with it too, through its REST interface.

You thought it's just for wordpress.com?

I did. There wasn't anything I noticed in the announcement about wordpress.org. Can you point me to where they mention it's being integrated into the wordpress.org codebase? [I'm aware of the mention about the jetpack plugin in the wired article]

>There wasn't anything I noticed in the announcement about wordpress.org. Can you point me to where they mention it's being integrated into the wordpress.org codebase?

The linked article is just the (lead?) developers recount of how they've built it.

The official reveal is through the project's site: https://developer.wordpress.com/calypso/

According to https://developer.wordpress.com/calypso/ the jetpack plugin is required for wordpress.org users (mentioned that above) and it sounds like you need to use their node.js hosting. (the point of .org is self-hosting)

So this all goes to my original point that there is very little clarity on where this leaves wordpress.org. It's clearly a big endorsement of node.js, which is great, but there needs to be some clear strategic intent here for where we're headed with wordpress.org - beyond what seems to be a band-aid.

This is open source. You can run it locally, host it yourself, put it on Heroku -- whatever your heart desires. And, yes, you can always just use WordPress.com (for free, btw). And that's just out of the box; The sky's the limit if you get involved as a contributor (and you should!)

Where does this leave WordPress.org? Well, let's put it this way: There will be a lot more people building cool things on top of the WordPress.org REST API now that this project has shown what can be done (I expect that over time the REST API will accumulate all the abilities of the Jetpack API)

Does there have to be a better strategy for WordPress.org? I don't fear for a project that has already claimed 25% of the web and is growing market share faster than any other CMS.

Reply on news.ycombinator.com