pauldotknopf

They also print advertising without your knowledge.

http://www.dailytech.com/HPs+Web+Connected+Printers+May+Prin...

It knows which properties are accessed in each component, and ensures only the ones that rely on the changed data are updated.

This is what blew me away. I understood that "computed" values were doing this, but when I saw that the react components were using it as well, I was sold. I have been in componentWillReceiveProps with redux too much, trying to improve rendering performance. With mobx, out of the box, you get 100% exact render updating.

Wow, your project looks great! I will be using it for inspiration in the future for mobx!

Exactly, you can treat Gulp like the a pure make system, and do whatever you want in each target.

But my point is that you can use gulp only (no plugins), and throw your npm scripts into gulp tasks.

Where is the risk there?

There is a large amount of stuff to know before you can develop and debug the piping stuff in gulp, I grant you that.

But, what are you going to wind up using in npm scripts for your resource compiling? Webpack? Browserify?

Why not put that all into a gulp file? Gulp files are great for non-piping-streaming tasks. It has great support for chaining tasks and making tasks dependent upon others.

What benefit do I get by actually moving to npm scripts, that I couldn't have in a gulp file?