News for hackers. Stuff that matters.
Re:Twenty years later I wrote a Tetris again by userbinator on Sunday October 23, 2016 @01:04PM (#12774322)
Yes because with improved tools we are expected to do more things to achieve the same goals.

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.

Re:Twenty years later I wrote a Tetris again by bane on Sunday October 23, 2016 @02:52PM (#12774824)
The demoscene is amazing fountain of technological progress. I feel sometimes like it's the abstract math of the software world, off doing lots of very impressive useless stuff, until some little piece of tech filters its way down and revolutionizes part of an industry. For example, lots of sceners now are bringing things like procedural generation of art assets to the masses, but it's been a common technique in the scene for decades.

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

Re:Twenty years later I wrote a Tetris again by jbpetersen on Sunday October 23, 2016 @04:42PM (#12775329)
That generalizes well to any exercise in restraint contributing valuable approaches to the issues it highlights.
Re:Twenty years later I wrote a Tetris again by notgood on Sunday October 23, 2016 @05:15PM (#12775460)
>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.

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.

Re:Twenty years later I wrote a Tetris again by _adamb on Sunday October 23, 2016 @09:43PM (#12776339)
By "more things" the author doesn't mean "inefficient work that produces no value." She actually gives the example that her old code produced solid squares with a border & the new ones are generated with some visual effects.

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), ...

Re:Twenty years later I wrote a Tetris again by taneq on Monday October 24, 2016 @02:00AM (#12776959)
Yeah, it's much more defensible a statement if you read it as "our expectations from code have grown exponentially" than if you read it as "it's exponentially more complex to achieve the same goal".

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.