pieroxy

I needed something similar for a javascript project and stumbled upon this excellent library by pieroxy that worked flawlessly: https://pieroxy.net/blog/pages/lz-string/index.html base65536 looks pretty similar to that except that base65536 is not as much focused on compression than it is on "copy-paste-ability". Shoco is another excellent library that comes to mind for shorter strings: https://ed-von-schleck.github.io/shoco/

It's probably similar to this: https://pieroxy.net/blog/pages/lz-string/index.html Check the 'How does it look?' section.

Look under "More Features" of the main website[0][1]. > kabas.online can be opened passing a programm within an URL parameter If the author of the language reads this: you could try shortening the URL with LZString[2]. [0] https://kabas.online/main.html [1] https://kabas.online/run.html?title=Run&code=sz%20%3D%20100%0Acolo… [2] http://pieroxy.net/blog/pages/lz-string/index.html

Why not `zip blah.zip blah.html` and do it all as a single html doc? http://pieroxy.net/blog/pages/lz-string/index.html https://github.com/pieroxy/lz-string/blob/master/libs/lz-string.min.js ~5kb gets you an lz-decoder, and you should be able to pull a bunch of trickery with blobs and compressed strings to get somewhere?

I can't speak to whether it is used more often, but I would bet the java-based Nashorn vm is significantly slower than the c++-based nodejs. In fact, a cursory google search shows this is the case, and it's not even close. See: http://blog.jonasbandi.net/2014/03/performance-nashorn-vs-node.html http://pieroxy.net/blog/2015/06/29/node_js_vs_java_nashorn.html (I can't speak to the quality of either of these tests, but the results seem decisive)

Yup on all accounts, although: > Not if you want to store more than few MB (5 or 10 max depending of browsers if I recall) There's a case for something like http://pieroxy.net/blog/pages/lz-string/index.html which can save up a lot of space

http://nodeca.github.io/pako/ http://pieroxy.net/blog/pages/lz-string/index.html

I use Pocket, Instapaper may work aswell. http://lifehacker.com/5894995/bookmark-and-read-later-apps-compared-re… http://pieroxy.net/blog/2014/10/05/reeder_and_its_companion_apps_reada… http://recode.net/2014/06/09/read-this-when-you-actually-have-time-a-g…

If you're purely interested in client-side compression in the browser (i.e. compatibility with server libraries/filesystem tools is not important) it's possible to get better compression in less time using http://pieroxy.net/blog/pages/lz-string/index.html

I've been using LZString for data I put in LocalStorage. Obviously you can still hit the limit, but it takes quite a bit longer. http://pieroxy.net/blog/pages/lz-string/index.html