Open Menu
AllLocalCommunitiesAbout
lotide
AllLocalCommunitiesAbout
Login

Implementing Tic Tac Toe with 170mb of HTML - no JS or CSS

⁨129⁩ ⁨likes⁩

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨mac@programming.dev⁩ to ⁨programming@programming.dev⁩

https://portswigger.net/blog/tic-tac-toe-in-html

source

Comments

Sort:hotnewtop
  • addie@feddit.uk ⁨1⁩ ⁨year⁩ ago

    Well now. A few things, here:

    • there are not 9 × 9 × 9 × 9 × … possible ways to play. After the first move, 8 squares remain, and so on, so there’s at most 9 × 8 × 7 × … = 9! = 362880 ways that the game can be played, ignoring the fact that most of those can be eliminated as reflections and rotations, or as win positions before you fill the whole board.

    • we don’t care how we got there. Each square can either be blank, a cross, or a nought, so 3^9 combos = 19683, and most of those are illegal, as only the boards where there’s (one or zero) more crosses than noughts are good. And you don’t need to store ‘the computer’s move’, just jump directly to letting the player go again. Let’s guess we need at most a quarter of that.

    • we could have created a single web page with 5k anchor elements on it back in the HTML 1.0 days, ignoring the fact that it would have taken a while to download on our 28.8K modems. That wouldn’t have been 170 Mb of unnecessary tagging, even with the ‘lay it out with tables’ style we had at the time.

    Google do seem to have a predilection for reinventing the past, poorly. I hear that their bonuses are based on inventing ‘new’ things, though, so it’s in their interest to pass it off?

    source
    • Treczoks@kbin.social ⁨1⁩ ⁨year⁩ ago

      Indeed. One could have done the whole thing with a simple, static HTML page.

      On top an empty board with 9 clickable fields. Each of them links to a new, pre-rendered board on the same page, with the move of the player and the perfect reply of the computer already in place, and 7 clickable fields. Which link to other, pre-rendered boards with 5 clickable fields remaining, then with three. The last one only has one field open, so this could be pre-filled as a player move.

      All in all this would result in 9x7x5x3=945 pre-rendered boards max on that page. And, of course, two links to "You won" and "You Lost". I'm no HTML junkie, so I have no idea how many bytes one would need to produce such a board, but I'm sure this all could easily done way below 170MB.

      source
      • kogasa@programming.dev ⁨1⁩ ⁨year⁩ ago

        Some of those boards are impossible, and there are multiple ways to get to most of them, so you only need maybe half of that.

        source
        • -> View More Comments
    • floofloof@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      170 Mb of unnecessary tagging

      The guy in the blog says mb (millibits) and you say Mb (megabits). I was confused so I checked, and the page is 170MB (megabytes).

      source
      • interolivary@beehaw.org ⁨1⁩ ⁨year⁩ ago

        The guy in the blog says mb (millibits)

        a) does anybody actualy use that? How many people reading this thread can say they’ve actually seen that in real use or used it?

        b) I’m fairly convinced you knew what was meant because it’s not like it’s uncommon to use a minuscule m for “mega” in colloquial usage

        Weird performative pedantry or a joke that flew past my head? I give about a 0.5 probability for both

        source
        • -> View More Comments
  • clearleaf@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Modern web development in a nutshell.

    source
    • eager_eagle@lemmy.world ⁨1⁩ ⁨year⁩ ago

      ahem excuse me?

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

      source
  • choroalp@programming.dev ⁨1⁩ ⁨year⁩ ago

    170 MEGABYTES. Excusez moi?

    source
    • interolivary@beehaw.org ⁨1⁩ ⁨year⁩ ago

      I mean, wouldn’t it essentially have to be storing every possible move 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

      source
      • coloredgrayscale@programming.dev ⁨1⁩ ⁨year⁩ 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.

        source
  • zout@kbin.social ⁨1⁩ ⁨year⁩ ago

    Sorry, but, mb, in lowercase? Like millibit?

    source
    • kinttach@lemm.ee ⁨1⁩ ⁨year⁩ ago

      “I implemented the FizzBuzz algorithm in only 10 million lines of code!”

      source
      • cbarrick@lemmy.world ⁨1⁩ ⁨year⁩ ago
        char* fizzbuzz(int n) {
    switch (n) {
        case 0: return "fizzbuzz";
        case 1: return "1";
        case 2: return "2";
        case 3: return "fizz";
        case 4: return "4";
        case 5: return "buzz";
        ...
    }
}
        source
        • -> View More Comments
    • clearleaf@lemmy.world ⁨1⁩ ⁨year⁩ ago

      For comparison the original StarCraft game asks for 80 uppercase megabytes of HDD (76.294 of whatever we’re calling the lowercase thing today) and for RAM it asks for 16MB/15.259mib.

      source
      • cbarrick@lemmy.world ⁨1⁩ ⁨year⁩ ago

        whatever we’re calling the lowercase thing

        • M: “Mega”: 1000^2
        • Mi: “Mebi”: 1024^2
        • m: “Milli”: 1000^-1
        source