I would disagree w/ your comments that HTML5 "is better" than Flash. The main reason why HTML5 could be construed as "better" is the open-source factor.
HTML5 is nowhere near as capable as Flash. In many aspects, HTML5 isn't even in the same solar system in regards to capability.
The HTML5 vs FLASH thing was purely a political play - tech/performance had nothing to do with it. Of course Flash is a CPU/RESOURCE hog --- it has to be since it has a handful of built-in video codecs such as H264 and VOIP codecs such as MPEG4/3. Since Flash 10.3, Adobe integrated an acoustic echo-cancellation (AEC) module within the plugin so you don't need a headset/ear-buds for real-time communication. That AEC module intensely sucks up CPU resources -- especially if it has multiple streams to cancel.
Here's a list:
http://helpx.adobe.com/flash/kb/supported-codecs-flash-player.html
Here's the bottom-line: Everyone is cooking with water and everyone has the same ingredients.
Once HTML5 catches up to Flash in regards to capability, it too will also be a massive CPU/RESOURCE hog.
HTML5 is years away from catching up to Flash. It too will also have its trials and tribulations in regards to stability and performance.
HTML5, at this point of time, still has no real viable API for multi-directional voip/video communication. WebRTC is currently limited to 1:1, whereas Flash is basically unlimited. WebRTC also has no mechanism for AEC. It's very, very limited.
In 2000, I founded one of the nation's first real-time online college services geared for gifted/advanced students that later evolved into a web conferencing company. Our intellectual property is based entirely off of Flash. We use Adobe Air to push our mobile apps to iOS/Android.
I'm very educated on what HTML5 is and what it can do - and more importantly -- what it can't. I'm not saying any of this as a "Flash fan" -- in fact, I'm quite the opposite. For every enterprise server I put out into the field, I have to pay Adobe $4500 per AMS license. As our cloud service grows, I have to pay the same to build-out our origin/edge RTMP clusters. On top of that out-of-line pricing, Adobe seems to put out buggy Flash player versions just to have the world act as their beta testers. I've been the recipient of a lot of client angst due to them putting out shit-versions.
In short, if someone handed me a box with a million dollars in it, there's no way to replicate the intellectual property we have now within HTML5 today. When HTML5 is at least half-way there, we're going to begin the grind on an HTML5 prototype. By the time we're on version 3 or 4 of our HTML5 service...guess what.... HTML5 will be a resource/CPU hog as well.
Also, Flash works perfectly on Macs. There are no performance issues with Flash and Macs (hardware-wise). In fact, Macs run Flash far better than most Windows systems. Any performance issue on a Mac is likely caused by having "Hardware acceleration" set to "ON" within the plugin settings. For most Macs that needs to be set to OFF since they don't need it and it causes "jitter" when enabled. Chrome is the worst browser to use - Firefox (imo) is the best. Safari - nobody really uses that, so who knows.
Dave