Remix.run Logo
teaearlgraycold 5 days ago

For modern applications you’ll have better ways to maintain state. As shown they cause trouble in practice. Cookies should be used sparingly.

prokopton 5 days ago | parent [-]

If you want to maintain state across navigations and share that state with a server it’s the best we’ve got.

bpicolo 5 days ago | parent [-]

Server can store session state

telgareith 5 days ago | parent [-]

Server side session state for more than authentication is way worse than "code smell."

It requires a ping to a shared data source on every request. And, the same one for all of them. No sharding, No split domains... That gets expensive fast!

naasking 4 days ago | parent | next [-]

You just described how the whole web operates. It works just fine.

MBCook 4 days ago | parent [-]

Even if you want client side, we have better ways now than cookies.

inopinatus 4 days ago | parent [-]

We do, but only cookies are universally available. Plenty of unusual user-agents in the world, or people like me that browse with JS off by default.

CrimsonRain 4 days ago | parent | prev [-]

I add some products in phone. Then I login to desktop later for modification and order. Cart is empty. That's engineering smell. A really bad one.

telgareith 4 days ago | parent [-]

Thats nothing more than UX/UI.

> In computer programming, a code smell is any characteristic in the source code of a program that possibly indicates a deeper problem. Determining what is and is not a code smell is subjective, and varies by language, developer, and development methodology.

- https://en.wikipedia.org/wiki/Code_smell