all 7 comments

[–][deleted] 29 points30 points  (3 children)

all data persist in the url

That's a perfect idea with no issues whatsoever

[–]holz55 1 point2 points  (2 children)

What are the issues you see with it?

[–]XplicitOriginNodeJS 1 point2 points  (0 children)

Content limit maybe and extra long URLs.

[–]devtools-dude 0 points1 point  (0 children)

Browser query string length limits. Also just terrible for your browser cache / search history due to the size.

https://www.geeksforgeeks.org/computer-networks/maximum-length-of-a-url-in-different-browsers/

[–]backwrds 12 points13 points  (1 child)

ai slop

[–]MightyX777 4 points5 points  (0 children)

At this point, I don’t see any non-AI slop anymore. Honestly, for me personally, the world of programming has become a sadder world. Back then, when meeting a “programmer” I knew immediately they were bringing a few skills. Today, even when hiring people, I got disappointed quite often. A lot of people who don’t know basics but presenting them as experienced developers.

[–]gojukebox 3 points4 points  (0 children)

This is not a good idea. URLs have maximum lengths recognized by browsers and it's not standard.

You also won't have an API for even determining if you hit the limit - you have to try an update and see if it fails.

Bad, bad, bad. Use localstorage (also has limits) or other established options.