• Eager Eagle@lemmy.world
      link
      fedilink
      English
      arrow-up
      28
      ·
      3 years ago

      ahem excuse me?

      modern implementation would have at least a 300mb node_modules/ and a bunch of memory leak sources

    • interolivary@beehaw.org
      link
      fedilink
      arrow-up
      4
      ·
      3 years ago

      I mean, wouldn’t it essentially have to be storing every possible move (well, state) for as many rounds as you want for the player to be able to play at most? And I’m not sure he can take advantage of the fact that you can end up in the same state from multiple other states, which would remove a lot of the redundant ones

      • coloredgrayscale@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        3 years ago

        Look at the screenshot at the beginning of the article. Every possible state is stored in a div, with the state encoded in its Id. So it’s possible to reuse such “duplicate” states.

        Strictly speaking, it would not be allowed for the same ID to occur multiple times.

  • tfc@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    3 years ago

    Doesn’t seem to work in Firefox? It just displays every combination lol