Job van der Zwan

> Is that ES6 versions tree-shakeable? That's really cool though - more browsers are supporting it all the time, plus useful for Webpack / Rollup :-) I tried making it...

We could also stick to one version equalling one format, then per format decide if and how to add more metadata, or settings like you said, or it's own sub-versioning...

Hey guys, my apologies, I've been sitting on this little hack since December. I wanted to clean it up first but maybe you want to try it out for yourselves:...

BTW, this is Uint8Array UTF16. I'm building a Uint8Array Uint8Array version.

Thanks, this is a known issue but we cannot merge this unfortunately :( The problem is that we cannot change this without breaking backwards compatibility. (also, definitely something to remember...

For a web-app I made a set of functions that lets you declare a simple schema and generate pre- and post-processing functions (called encode and decode) to turn known patterns...

> just add a version flag and check against that As Rycochet mentioned: that's not so simple because the current format is pure a raw compression string without any metadata....

The reason I'm opening this here is: gloryknight suggested adding 0 as the default separator char (meaning the actual the value zero, which is an unused char code, not "0",...

> Second argument for the `compress` would be a bit awkward, since the argument should be added to all of the functions (also binary ones) and passed down in the...

I did a quick test of my own idea of splitting *after* the separator. So far it seems to actually compress worse than your heuristic, sometimes even worse than default...