Come on man... really... it's right there. javascriptstreamingasynchronous. I'm not sure how many more buzzwords you need. those earlier losers who built make, gcc, and other tools just didn't know what they were doing. And with newer tech, everyone who's not streaming asynchronous javascript is a dinosaur luddite.
I didn't propose that. The point is to read the file once, then do multiple steps on it, and write it out just once.
I feel like this whole thread is a bad joke.
Do you know of Unix pipes? The fact that gulp calls all of this "streams" and "pipes" is a seriously bizarre form of NIH.
You might also be interested in make -j option.
pipes and streams mean something slightly more specify in a node context, but they are actually compatible with Unix streams, which shockingly enough also work well on windows meaning you can string together a make-like build system which works on windows as well (easily, make is not easy on windows)
Not sure what you mean. I've developed Android apps on Windows 7 using Cygwin and make just fine. It's nearly identical to using it on Linux.
You still have to install Cygwin, other solutions require no .dlls
No .dlls, just rewriting everything in Javascript. Because that's so much less invasive than a dll to let you use existing mature solutions
If only the operating system had some facility to store a recently read file in RAM, so it didn't have to read it from the disk the next time. That would be a real innovation!
(sarcasm)
Page caching: it's been around for a while. At least on unix systems. I imagine Windows, etc have it too.
yeah,it's called piping and supported natively in make.