buffers

Which in turn means you can't preallocate buffers because you don't know the sizes in advance.

Early TCP implementations allocated all the resources for a connection, including the big buffers, when a SYN came in.

Ease of writing filesystem drivers means you find stuff like FrexxEd - a text editor that exposes the open buffers as files, so that you can operate on the open buffers with any tools that can process a file.

For an example of the kind of improvement, think about how depth buffers are implemented.

Thrift was designed based off of protocol buffers, but handles everything from end to end.

While this is something you have to deal with anyway in multi-machine systems (think network buffers) it's an unnecessary worry in single-machine ones.

For example, Protocol Buffers is binary too, but requires unpacking, causing lots of object allocation, etc.

That also allows you to construct more complicated objects like buffers natively.

Some thoughts: What you call tabs are what vim calls buffers.

A performance penalty and kernel memory management complexity comes from peripherals and kernel's inability to directly address all memory and resulting need for bounce buffers.

The size of the jump buffers on ia64 terrifies me.

I also suspect Go's results may be different and closer to what you are doing if you used go channels with buffers.

"Progressive streaming" at the server side generally doesn't require any configuration at all in TCP -- the client reads what it wants, the buffers fill up, and the transmission stalls on a missing ACK.

Yes, it is true conceptually, but: 1) "Who cares" is not the sort of thing you want to say to someone who cares about performance because: 2) Sending the data to buffers for subsequent reduction was the first implementation (2009).

Typed Objevts would let you have objects where properties are of a static type (int8, Boolean, string) and they are stored using Array Buffers.

Buffers are the proper solution to the mentioned comment.