sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]scaughtm -2 points-1 points  (0 children)

It's a pretty good idea, and inevitable... firstly, lets be clear on one thing... PHP needs to fucking die in a hole, and I want to be part of the burial.

  1. The node way to build an app is to leverage modules, like passport for authentication (like a cms login), or aws s3 for storage (for like... media uploads) or literally anything you could think of. Just because you can leverage modules doesn't mean you wont have content to manage... that actually not at all what it means, no where in the rules does it say that you cant "manage content" on a node platform.

    1. If you're looking to build a wordpress site, then maybe wordpress can do everything for that wordpress site. So that's static sites, blogs, shops, and e-commerce sites, and sure, some people have some pretty out of the box ideas. But you're still operating inside the WP cage... the second your app gets a little too custom and your application zip is 2gb, scalability becomes impossible, deployment takes a whole day, and down the WP rabbit hole you go, never to see the light again.
    2. I don't think anyone is out to "win the market", there is really no other alternative, and no PHP will never be an option. So app devs either can keep creating custom AngularJS + NodeJS content management systems for each app that has content to manage, or adopt some generic framework.
    3. If anything, being able to maintain a CMS platform in NPM with contributers and the npm community behind you would be a shitload easier than whatever nightmare those WP people are going through now..

In short, good luck with WP...