3 ms·
Once you've already given up on human-readability, it probably doesn't much matter how long/gross the result is. Rather than spending effort and adding complexi
by mikepurvis 4y ago
Once you've already given up on human-readability, it probably doesn't much matter how long/gross the result is. Rather than spending effort and adding complexity, just provide a built in URL shortener.
- hot_gril 4y agoI agree, same reason people use json in the first place despite the inefficiency, it's easier.
- wtetzner 4y agoWell, there are limits to the lengths of URLs in much of the internet’s infrastructure, so better compression could still be useful.
- jsvaughan 4y agoThis is the critical point to make. Paste a few long texts into the boxes and the url goes into the hundreds of thousands of characters long, whereas this says that anything more than about 2000 chars puts you into uncertain territory: https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers https://stackoverflow.com/questions/417142/what-is-the-maxim...
- p1necone 4y agoIsn't storing state in urls and then using a url shortener just a key/value store with extra steps?
- taneq 4y agoBut with added session id energy too!
- mikepurvis 4y agoTrue, though I think the differences around shareability matter— a mapping-table entry is immutable, whereas even a non-logged-in session token is probably not.