There are a few things that bug me about this flame war:
1. I didn't realize Aperture was in any way supposed to be a Photoshop killer? It's an extended version of iPhoto - there to manage digital assets and provide some reasonable re-touching tools. Photoshop is used just as much to build content from scratch as it is to modify existing content.
2. The Flash plugin is CPU intensive and buggy on any platform, not just MacOS - it's a byproduct of it's cross-platform nature, the plugin has to dynamically re-compile code as it runs which is a resource intensive process - much like Java.
3. Flash stepped into the breach when there were no alternatives, Adobe/Macromedia should be applauded for that. Prior, releasing video content online that could be played in every browser and on every platform was near impossible, or, worse, involved the use of RealPlayer or Windows Media.
4. There is now a better alternative - that's HTML5. Just like flash put an end to the embedding of Java applets in web pages years back, so to will HTML5 eventually kill Flash off. That's not a problem, it's not because Apple is mean or Adobe is being hard done by - it's evolution in the technology sector. One day Adobe may release a platform that kicks HTML5 to the curb.
5. The Flash IDE isn't really what I would call 'Robust' in fact, it's anything but. It's an IDE targeted at non-developers, kind of a bridge between the design world and the code world. It did that job well for those particular users, but, it's been abused and Flash has been called upon to do things it really can't and shouldn't - this, in many ways has lead to the current performance and stability issues, the technology is being over-extended.
6. There is nothing stopping Adobe from pulling Mac support, but, as you all realize, it would be a silly move to make. You can't turn around and alienate more than 50% of your market due to a technology dispute. It's commercial suicide. There is however also nothing stopping Adobe from taking a step back, evaluating their Flash product AND HTML5 and perhaps releasing a flash-like editor/IDE that produces HTML5 content but with Adobe tools that are familiar to millions of Flash developers and devotees.
7. This will probably get me kicked - but - Those that make entire websites from flash movies should not be developing websites. Period. If it breaks the 'Back' button, it's wrong (Same goes for the over-use of AJAX) Just because you can, doesn't mean it's the best idea, or, even that you should.
8. The references to Apple becoming like Microsoft are a little perplexing - were Apple to become more like Microsoft, it would be a "Come one, Come all" environment, no restrictions on compilers/user interaction/quality - and, well, we've all seen how that's worked out for Windows users - glaring compatibility issues, huge UI inconsistencies, performance problems and a myriad of IDE/Language/Compiler combinations that often don't perform as advertised.
It's simple, from what I can see, Flash has been, now it's going and soon will be gone. Apple is trying to drive adoption of a better technology that it sees will improve the end-user experience for hundreds of millions, not only Mac users.
When a much loved technology - like Flash - begins to get sidelined and millions of fluent flash developers suddenly find themselves less relevant, well, there is going to be a huge fuss. The smart ones will simply move with the times, embrace the new technologies and probably keep using Illustrator/Photoshop/InDesign to generate the image components of their content.