I used to love getting the monthly Amiga magazine CDs so I could play around with the latest Amiga browsers and look through all the website content they had archived onto the CD for readers to look at offline. At the time not that many people were online and I definitely wasn't at home until 1998. All I had was access to the fast internet at university at the time (1MB/s in 1998 was amazing and still faster than many people's broadband today).
Regarding Flash, I have been a Flash developer since the first Macromedia Flash 3 came out and loved the software in its early days, and on to version 4 and the birth of Actionscript. At the time I was a Multimedia Director developer, mostly making quite heavyweight CD based interactive presentations for business to business presentations, and Flash was the first platform to truly offer similar capabilities as Director, but online in a browser. This was quite amazing at the time. The difference is that back in the 90's when Flash was launched most people had 56K dialup internet and good developers become very good at optimising their code and graphics to load quickly on low bandwidth. Flash workd well in these early days on 68K Macs and Pentium 2 PCs. The bad press Flash received came later when Macs and PCs started to get more powerful with the P4 and PPC processors. A lot of developers got very lazy or just didn't have a clue about optimising their code and graphics, because they had broadband and a faster CPU so didn't care or realise than many didn't have these and their Flash files were bringing webpages to their knees on home users computers trying to load the SWF files.
And this is the whole problem more recently. Most people are clueless, lazy or both! They don't optimise graphics, they don't optimise and test code. The make something and if it works locally on their computer they consider it done and just throw it online. This isn't Adobe's problem, it is those developing on the software and creating bad code and bloated assets within the flash files that crash or slow down the Flash player on any platform trying to run the files. Sadly this has backfired onto Adobe with everyone blaming them, instead of the lazy people creating the bloated unoptimised flash files.
And no. HTML 5 is not a replacement for Flash.. it can only currently achieve about 5% of the features and abilities of Flash. But for the majority of things most people actually used Flash for HTML 5 can be used as a replacement. But I bet they still don't optimise their projects and even that ends up a bloated mess.
My biggest hate online is people's lack of consideration for the content they upload. Everyone needs to optimise. Even if you are just uploading an image to a forum please don't try to attach the image directly from your camera. This will be 3000+ pixels wide and 10+MB in size. Even most people's broadband can't cope with these very well, and most monitors can't display more than a 1000 pixel image fullscreen so why bother? Reduce and optimise your images people. 800 pixels wide and 300KB should be the limit. It drives me mad.
As for the Amiga running Flash.. forget it. It was never fast enough to play an SWF flash file. The Amiga just doesn't have the processing power to do it. Flash never ran smoothly on anything less than a 400MHz P2 or 333MHz PPC Mac back in the 90's so thinking you could run it on a 50MHz 030 Amiga is never going to happen. The hardware on the Amiga was already years out of date before Flash arrived.
- - - Updated - - -
And the flash player has and will always be closed source, so you will never see it ported on any new/old hardware.
That isn't 100% true. FLA is closed source, so software developers can't see how the actual FLA files used during the development of a project work (and hence how Flash itself works), but the resulting SWF files have not been closed source for some years now. Adobe made the SWF format opensource a long time ago so that other software developers could add the ability to output/save their projects as SWF files. The release of SWF was the reason sites like Youtube suddenly appeared, using the SWF filetype to run their videos.
Alternative players exist.
Firstly look at the open source library
gameswf http://tulrich.com/textweb.pl?path=geekstuff/gameswf.txt
And then some of the alternative players such as:
Gnash;
http://www.gnu.org/software/gnash/
LightSpark;
http://lightspark.github.io/
Unity Web Player (I think this has now evolved from an alternative content player into a games development platform utilising flash technology);
http://unity3d.com/webplayer/