[HN Gopher] Remix's concurrent submissions are fundamentally flawed
___________________________________________________________________
Remix's concurrent submissions are fundamentally flawed
Author : bo0tzz
Score : 72 points
Date : 2024-09-12 12:47 UTC (10 hours ago)
(HTM) web link (dashbit.co)
(TXT) w3m dump (dashbit.co)
| hyeomans wrote:
| Jose Valim nails it: Remix's concurrent submissions have a
| fundamental flaw. Without causal ordering, you're stuck with race
| conditions and stale data, leading to poor UX. They need to
| rethink their approach or embrace causal ordering to fix this.
| pheeney wrote:
| Is there a GitHub issue or discussion to subscribe for updates
| from the Remix team on this topic?
| aerox_zero wrote:
| You can check the ChatGPT frontend source code that they do not
| use Remix's actions (submission and revalidate mechanism). And
| the fe does only one request to receive the data for chat. The
| mechanism has benefits like working without javascript and issues
| but you can avoid it if you dislike it. Did the author has
| checked it's own theories about why ChatGpt may be slow before
| making such arguments?
| mtndew4brkfst wrote:
| Jose seems to be far far far more enamored with ML than Elixir
| these days. Burnout and boredom happens, I get it, but it's still
| a bummer to see.
| klysm wrote:
| Embracing the platform can hurt when the platform sucks
| azangru wrote:
| Which part of the problem described in the post, would you say,
| is caused by the platform?
| hollerith wrote:
| Wikipedia say, "Remix is an open source full stack web framework.
| The software is designed for web applications built with front-
| end JavaScript frameworks like React and Vue.js. . . . Remix has
| been presented as an alternative to the popular React framework
| Next.js."
___________________________________________________________________
(page generated 2024-09-12 23:01 UTC)