6 ms·
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.
by nawitus 13y ago
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.
- camus2 13y agoyeah,it's called piping and supported natively in make.
- nawitus 13y agoI stand corrected :).
- aryastark 13y agoI 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.
- cwmma 13y agopipes 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)
- aryastark 13y agoNot 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.
- markrages 13y agoIf 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)
- gyepi 13y agoPage caching: it's been around for a while. At least on unix systems. I imagine Windows, etc have it too.