I'm really excited to see how this goes because the "static" YAML config for a typical Agent setup (e.g. scrape metrics from pods in a Kubernetes cluster) is quite verbose and difficult to figure out unless you already know exactly what you're doing. I always end up having to find somewhere to copy/paste it from :)
Representatives and direct Taxes shall be apportioned among the several States which may be included within this Union, according to their respective Numbers, which shall be determined by adding to the whole Number of free Persons, including those bound to Service for a Term of Years, and excluding Indians not taxed, three fifths of all other Persons.
The Redis protocol uses length prefixes for bulk strings and arrays (per your linked document). That enables it to read multiple bytes at a time off the socket, though it does seem like you'll still end up doing a bit of character by character processing with the result.
RESP uses prefixed lengths to transfer bulk data, so there is never a need to scan the payload for special characters like it happens for instance with JSON, nor to quote the payload that needs to be sent to the server.
The Bulk and Multi Bulk lengths can be processed with code that performs a single operation per character while at the same time scanning for the CR character, like the following C code:
I've found using minimization to give up 40% smaller files even after gzip. Even so, combining multiple JS or CSS files into single one and using image sprites will probably be your biggest win.
I'm really excited to see how this goes because the "static" YAML config for a typical Agent setup (e.g. scrape metrics from pods in a Kubernetes cluster) is quite verbose and difficult to figure out unless you already know exactly what you're doing. I always end up having to find somewhere to copy/paste it from :)