Cool, we have the technology and know-how to replicate a 1984 video game using the hottest JS framework.
Does no one care what is the result as long as the developer put the "right" abstractions in making it?
Does no one care what is the result as long as the developer put the "right" abstractions in making it?
Plenty of take aways from this Show HN for me. I can look at the code and understand how React was used to achieve this. Sure, this could be done with 100s of other frameworks or even plain C++ but thats not the point. But again, you missed the point.
I think it's a very cool project.
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).
We've seemed to replace the merits of direct functional efficiency with a novelty of complexity.
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.
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.
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.
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.