Job van der Zwan

@tophf: can you show me what the faster `Map` and `Set` code looks like? Because when I added `Map` to my previous benchmarks it turned out much slower than even...

Thanks, pretty straightforward. I guess the reason they're not faster in my benchmarks is because I'm limiting myself to 64 single-character keys. Still, the `charCodeAt()` optimisations are kind of orthogonal...

> The stack is still used for the arguments passed via .apply so anything larger than 32k is a risk depending on the browser. And even that is a risk...

Some more thoughts on that de-opting: ```js let factory = function(){ return function(){ return 0; } }; let a = factory(); let b = factory(); let c = a; a...

> Just as a side note, be careful when you advertise a x2 increase. Right, I should have been more clear that I when I talked about 2x/3x speed-ups was...

At least the bugs are funny: 

So I figured out a simple way to do in-browser line-by-line performance testing: inline `lz-string.js` into `SpecRunner.html`, open the latter, then use the browser dev tool to measure performance for...

So just to add to pieroxy's remark that this is complicated, I did some in-between benchmarking on Chrome and Firefox. I'm using all the test strings except Hello World, so:...

I hope my long comments don't feel like spam - I code better if I write out my thought processes, plus I think it helps clarify what I'm changing and...

So I've looked at `compress` again, also Line Profiling it, using `aaaaabaaaaacaaaaadaaaaaeaaaaa` as the test string. I'd like to zoom in on one particular part (for completeness, [here is the...