[wasmperson]

In gamedev, "optimistic updates" are called "client-side prediction," and are a standard part of multiplayer games. IMO it's somewhat risky to apply the technique to web-apps, since each network request typically corresponds to some important operation, and optimistically updating the UI is lying to the user about whether that operation completed successfully.

IMO a good approach is to update the UI immediately but still show some indication that the operation hasn't completed. So in a chat app, for example, add the message to the list of messages, but with contrast reduced slightly to indicate that other people can't see it yet.

[artman]

Operations are on average applied within a few hundred milliseconds, and almost never fail. Because of this we treat the success path as default, and indicate that your changes haven't been applied only if we detect that you're offline, or if it takes more than 4 second to apply the changes.

[epolanski]

I see this comment over and over again, yet I know lots of Linear-enthusiastic people and none is suffering of this.

Meanwhile after a brief period of Jira being performant, it has felt into ruin again.

In any case, I've tried both, and Jira is on another whole level when it comes to map processes of different teams.

Linear is a good looking toy mostly catered to the average software engineering team, it just doesn't support the flow complexity needed by different business units.

[ggambetta]

I was thinking exactly the same thing, this is CSP/SR. One of my favorite topics! https://gabrielgambetta.com/client-server-game-architecture....