- Minification: Uglify
- Transpilation: Babel/TypeScript/CoffeeScript
- JS Module Systems: Require/Browserify/Webpack/JSPM
- CSS preprocessors: Less/Sass/Stylus
- Linting: JSHint/ESLint/CSSLint
If you're using a lot of front-end tools, you're using Node. And if you're using Node, you might as well use it to write your APIs.
Cloud9 I guess would be a good example of a killer app ,but that's no CMS.
The reason why there is no serious CMS with node is that nodejs development is extremely hard, because async programming is hard. No matter how much layers one puts on top of it (promises,generators...) you can't abstract async programming in nodejs.
Look at Go, Go routines can be totally abstracted. IF I write that code:
result := Object.DoNonBlocking()
As a client of Object I don't have to know whether it is run concurrently, or not , or blocking or not. In node I have to know whether I returns a promise or a value , IE hump into the event loop or not.PHP has its share of problems though,just like Go, but their concurrency model(or lack of) make things way more easy.
I can't imagine writing something such as Magento or Drupal in nodejs (with the exact same features). It would be just insane. A great challenge though.
At this time Javascript's biggest strength is build tools. It may not be as mature as PHP on the server, but there is so much community growth that I don't think it will be long catching up.
The fact that there's at least 4 "mainstream" build tools and their popularity changes every 6 months is a sign of an ecosystem with little stability that is no good to build a solid foundation.
On Ruby and Python land, how long has it been since RoR and Django have been the dominant players?
No, not when I have access to all kinds of other languages, frameworks, libraries, etc to choose from on the server side.
Unreal engine in asm.js <<< this would be a "killer app" for the platform as a whole.
> Wordpress, drupal, magento, phabricator, mediawiki, sugarcrm...
Very few apps are built from scratch using PHP unless the intention is to share the application code like wordpress, drupal, etc.
On Node, you're almost always building from scratch, rather than creating plugins for an existing application.
Apples and oranges. Different use cases.
Yes, there are. I didn't say there weren't. I think PHP is great, relax.
In my professional experience, however, I don't see people start a codebase from scratch in PHP anymore. It's almost always based on Node.
Err.. that's exactly what you said, no?
Well, yeah, if you work in a shop where node is the goto solution on the server side, that's going to be your experience.
There aren't any, really. Coupled with NPM it's great for building your own platform with custom requirements, but if you want to spin up an instance of something that already gets you 90% of the way there, PHP is a better choice.
"I will be honest. I use ghost as my blogging platform for about a year, and in comparison to wordpress... it just doesn't hold up. Everything from stuff as big as upgrading, mid range as plugins, and even simple things like spell check were overlooked (at least in the version I have). It kind of reminds me of the Pepsi Vs. Coke test. Went to it for that initial appeal of simplicity.. and now am very dissatisfied due to how much its lacking."
Similarly, Rails made Ruby popular.
(I won't call phabricator a "vastly popular, feature rich out of the box tools")
I think >99% of the people who wanted a website (blog/forum/etc) had to call an IT guy to get this running.
Now they just have to register for a SaaS and the most technical they have to do, is linking their domain to it.
These are vastly popular, feature rich out of the box tools in PHP, aka the "killer apps".
As I don't follow the node community, what are the killer apps on the node side? Im talking about a complete piece of software, where I would want to set up an environment not for development but for running an application.