the more i experiment with different designs for my own low-level i/o primitives, the more it starts to look like deno_std... maybe, *just maybe*, there was at least *some* thought put into designing it. though i still don't like how it's mostly tied to deno's internals, and how bloated and suboptimal the code itself is... i sure hope it will get better once they stabilize it, but considering that they straight up deprecated `@std/io` in favor of web streams makes me question that...