Job van der Zwan

I think you tagged the wrong guy, hahaha. I only did a teeny bit of code clean-up very early-on in this code-base's existence.

I think it's because it doesn't tell the system that it's a monospace font, the original font also had this issue: http://askubuntu.com/questions/210283/how-to-use-fixedsys-in-the-gnome-terminal-or-wherever-monospaced-fonts-are-requ

The good news is that the link above also has a solution :)

Glad I could help a bit, looking forward to the next versions!

BTW: > If you want, you can tweak one or more questionable features of Fixedsys. E.g., the zero character is shifted one pixel to the right. To shift it back...

Some benchmarks: plain compress/decompresss: http://jsbench.github.io/#2a07fd14b55d44291da4b06d3ba6e5c3 base64: http://jsbench.github.io/#da32b5d1100c24c7744bb58ca3fff440 UTF16: http://jsbench.github.io/#4029cae03b1e2fc06ad44e35f5bfca6b Uri: http://jsbench.github.io/#54c40822dabdbd46a93fb0b7ff6832d9 Uint8: http://jsbench.github.io/#14395aeb1f452cefa52b5f86b0f644c5 I'd say performance is.. probably a bit better, but also almost negligible within the margin or error....

The main issue is that it's not easy to see if it's significant in the larger scheme of things - perhaps all computation and memory allocation happens in the core...

Hmm, time to dive into this a little deeper and see if we can fix that. Still on sick leave anyway so this is a fun side-track :)

The thing I was referring to is that compress is passed a function, which itself is usually a closure. I suspect that level of dynamism prevents some deeper optimisations. This...

Related to that, I just realised there's another optimisation possible for Base64 and URI-safe compressors: don't use `charAt`, use `charCodeAt`. The reason is that looking up integers in hashmaps is...