REMIX'S CONCURRENT SUBMISSIONS ARE FUNDAMENTALLY FLAWED (WITHOUT CAUSAL ORDERING)

Summary from the TLDR Web Dev newsletter

Remix's approach to concurrent submissions, using a "submission and revalidation" pattern, is fundamentally flawed. It leads to unnecessary latency and introduces race conditions where the UI can display outdated information, even after users have submitted changes. There are two solutions: Causal ordering, which makes sure requests are processed in the order they depend on each other, and Persistence, where a connection is maintained between the client and server to guarantee ordered processing.