I disagree. A comparison of "higher resolution" in the terms of NES would only mean an increase in nametable size, not in binary size of program. Of course if "increase in resolution" also meant increase in CHR size or sprite count, or color palette size then you would be correct.

My point in NES or in modern software, the target resolution you want wouldn't have an affect on binary size.

  Having made NES games for fun before

So I am. You are right, a more fair comparison would be a tetris.exe perhaps. But my point would still stand, 60mb (and that is zipped amount) orders of magnitude higher.

I want to ask the same question, what is your point? Are you arguing that java runtime or several dependencies OP added is not an indication of modern software bloat?

I'm saying that the capabilities of the game in question and the original Tetris are also orders of magnitude larger, you just don't see them directly because you're biased to comparing this game to the original due to its visual and gameplay style, and that comparing the two to measure the value of "bloat" is an absurd thing to do.

Sorry but sand physics is probably doable in a few kb (yes, that's kilobytes) of JS.

This is different and simpler but just 140 bytes (not k): https://codepen.io/KilledByAPixel/pen/WNGQWZG

Nothing in that game justifies being more than 1mb (being very generous...) minified as a browser app.

Of javascript. Which has a stupidly large runtime that is certainly not just a few kilobytes.

Sorry, I have to make one last snarky comment. You can probably include entire firefox along with that a few kb of js and still make it under whatever that 60mb expands to :)

Sure, let's maybe make an electron app.

Ok, was mentioning without the browser runtime obviously.

Opionated take, but I believe that the web common runtime should be part of the OS nowadays.

Even without this, Tauri is 8Mb.

You're also ignoring the fact that most of this functionality happened in chips. That's not the case with modern machines.