This particular compo has a long history and lots of different challenges: http://www.hugi.scene.org/compo/compoold.htm
- A brainfuck interpreter in 98 bytes
- Nibbles in 48 bytes (some of the disqualified entry reasons are also equally interesting)
- Maze builders in 122 bytes
If you choose wisely your dependencies those are going to be a lot more reliable (incl. less bugs) than the code you can write in a few hours; because its code with tests, a large user base, etc.
Realistically, she could have produced some blur effect twenty years ago, but there were no good toolsets for doing it. Because of the "improved tools", developers can now create that effect with one or two lines of code.
Summary: "improved tools": These tools enable easy access to advanced functionality. "expected": Users expect beautiful tetris, not just solid color with a border "achieve the same goals": Really, the goal is to create a playable terris. The definition of playable has apparently evolved in these twenty years.
As an aside, generally I agree with your comments about the bugs. Libraries are implemented in python (bugs here), python is implemented in C (bugs here), C has a compiler (bugs here), ...
A hacked-out Tetris clone in QBasic is easily doable even today, just head on over to qbasic.net and download the old interpreter and away you go.
I would like to see, for comparison, "how many things" you need to do to build (from scratch, in QBasic) an entire new version along with bitmapped artwork and it's own custom control hardware.
Doesn't this mean we are becoming more inefficient? I wouldn't agree with calling those tools "improved", in that case.
About the size of the code: the code I wrote this time is roughly one third of the size of my original code which probably means it has less bugs and is more maintainable
That neglects to consider the fact that you are now depending on orders of magnitude more code than before, which from an overall perspective certainly doesn't mean "less bugs", and in fact could even make things more difficult to debug.
...and for something related but on the opposite direction, a competition on making the smallest (binary) Tetris clone that follows a spec:
https://files.scene.org/view/mags/hugi/compos/hc22fin.zip
The winners are 363 bytes.