| > Not if you care about state being consistent between all clients. No idea what you mean > Say you want a minimap, or a presence indicator, now I struggle to see where I said that you have to have everything and anything on the client. > Events up are fine if you batch them and 204 (i.e CQRS). In return you get a nice pushed based system that That you have to actually code, create, and maintain. > Whenever your program has to interact with external entities, don't do things directly in reaction to external events. Instead, your program should run at its own pace. No idea what this has to do with anything I wrote > You don't need optimistic UI, a fast server with an in process DB and a decent backend language and you'll be fine for a lot of use cases. Again, this hinges on the childish belief that the network is always there, is always fast, and is always low-latency. And none of these answer the question of why you would want to save "I showed a modal on the client" in a backend database. |