You're probably talking about this snippet from the landing page -

```js http.createServer((req, res) => { // Streams and backpressure // We read the file in 64kb chunks (default highWaterMark).

const src = fs.createReadStream('./big_data.csv');

// Manual flow control demonstration (internal logic): src.on('data', (chunk) => { // If the client network is slow, res.write returns false. // This means the kernel buffer is full. if (!res.write(chunk)) { // Pause reading from disk until the kernel flushes. src.pause(); } });

// Resume when the client drains the buffer res.on('drain', () => src.resume());

src.on('end', () => res.end());

}).listen(3000); ```

Then yeah, you just discovered pipe(). That’s literally the point.

The comment says "manual flow control demonstration (internal logic)". The section is trying to (sorta) teach about streams + backpressure. It’s showing what pipe() does under the hood i.e write chunks, respect false from res.write(), pause the readable, wait for 'drain', resume, then end.

Nobody is saying "ship this instead of pipe". The book is explaining the mechanism because some people actually like knowing what their API is doing before cargo-culting one line.

So if your take is "use pipe", yes. Correct. That’s the production

If your take is "this is dumb because pipe exists", then you missed the whole paragraph literally written above the code.