• bitfucker
    link
    fedilink
    arrow-up
    4
    ·
    8 months ago

    When you are writing some complex web app, you will wish you used a framework. Some web apps can have more than 50 pages with multiple states that depend on remote data to be locally cached and synced depending if you are online/offline. Framework can handle a lot of the heavy state management for you and even provide a nice UI component library. But I do agree that React is too much, but jQuery is being replaced by vanilla JS. That is why I usually use Vue. But for simple stuff, yes, Vanilla JS is pretty much good enough

    • uis@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      8 months ago

      No framework will make FSM for you. Managing state of web ui is not as hard as managing state of game.

      Using TCP for networking? Loss, retransmit, lag, you’re dead. Using UDP for networking? Loss, desync, you’re dead. Sending full game state? Congestion, loss, lag, dead. Doing sync right, but still pushing too much data? Congestion, loss, lag, dead. Also keeping on server you need not only track game state, but what game state client confirmed to receive.

      • bitfucker
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        Strictly speaking, the original commenter is talking about website but sure there is an FSM JS framework too (XState).