[omegote]

I honestly think he has a point. There are hundreds of implementations of Tetris for any kind of platform and technology. This is only noteworthy (for some, at least, not for me) because it's build with React.

By the way, it's pretty dumb and shortsighted to depict flash as a neanderthal, because both its capabilities and its ease of use are (were) way beyond what current JS frameworks offer today (and in the upcoming years, at least).

[kristopolous]

Not only, but it achieved this 20 years ago, on computers of 20 years ago, and on internet connections of 20 years ago.

We've seemed to replace the merits of direct functional efficiency with a novelty of complexity.

[watwut]

Unfortunately, flash became uncool and it seems that tech community lately value "cool" over, well, anything else lately.

[watwut]

Yup, react part makes it noteworthy, worth bookmarking and learning from. Also that this implementation is actually fun to play, most of them are not.

This is how people and communities learn. They do small projects to see what is achievable. There is nothing shameful about it.

About the parent poster: he is just an adult equivalent of a kid that came into the room, scrapped other kids drawings and told them they are all suckers. Otherwise said, just someone having emotional meltdown and taking it on the random people around. No reason to take him seriously.

[daliwali]

If this were a student project or an intellectual exercise to implement Tetris in an obscure language, good on them. I can respect that.

However it is undeniable that there are overkill levels of abstractions in play here, for the purpose of using what is currently the most commercially viable web framework. This is like taking FizzBuzz Enterprise Edition seriously for being written in Java.

>just someone having emotional meltdown and taking it on the random people around

I won't stoop down to your level of using personal attacks. You don't know me.

[lewisl9029]

> By the way, it's pretty dumb and shortsighted to depict flash as a neanderthal, because both its capabilities and its ease of use are (were) way beyond what current JS frameworks offer today (and in the upcoming years, at least).

You're taking his depiction of Flash out of context.

https://github.com/chvin/react-tetris/blob/master/README-EN....

He was clearly only comparing the different solutions in terms of audio capabilities.

I can appreciate how much of a gigantic leap in capabilities Web Audio API offers compared to HTML5 audio alone, so I can vouch for that part of his depiction.

I haven't ever worked with Flash audio, nor Flash itself in general though, so you may still be right about him being unfair and shortsighted in making that comparison in the context of audio capabilities, but I think it's still an important distinction to make if that was in fact your critique.

[omegote]

I know he was talking about the audio, but my critique works both about flash in general and about audio support in particular.

ELEVEN YEARS ago Flash was already capable of both playing and recording audio from multiple sources, using several different codecs and offering the usual bells and whistles you're expected to find in any multimedia framework (vis.eq., channels, etc). And everything working exactly the same way in every browser equipped with a flash player.

And I'm taking eleven years ago because that's when AS3 was released. Flash had considerable audio support before that anyway.