Should v2 change default highWaterMark value? Alternatives?

[bitinn]

If users are writing isomorphic apps, they are quite likely unaware of a major difference of backpressure limit between node-fetch (16kb, as set by nodejs) and browser fetch (at least 1mb, not consistent across browsers).

highWaterMark is basically a signal to upstream whether it should continue to push data (thus cause downstream to store more data in memory).

I wonder if we should raise this limit to 1MB. Though as I wrote many times before, eventually some users will push it to the limit and encounter the same problem.

So it's a problem difficult to troubleshoot by endusers without knowing the existence of such problem beforehand.

What do you think we should do?

related to #151.

[bitinn]

Note that it's also documented.