Any blob of byte is a state container

you can save so much data in the url, I like how pocketcal.com stores the calendar informations

Yes, but keep it less than 1024 chars in length.

Duh :)

is this not a basic rest principle? URLs and req/res bodies are the only way to transfer anything so they must be the way to transfer state

It’s kind of nuts this even has to be explained. I had a coworker I’ve been trying to teach good application design and React state is the first “crap bucket” he always reaches for. I had to explain to him, “when we put values in the Url we don’t need to use state, because everything is already stored right?” “Uhhh sure fine go ahead and change it.”

But what bugs me about it is that this isn’t even that novel or intelligent of a realization. If you’ve used a web browser you’ve seen the url change. Connecting that with putting values in the url shouldn’t be such a huge leap. This was for a simple search page.

How do I stop this sort of brain dead unrealized thinking?

[dead]

[flagged]