Linked by Kroc Camen on Sat 29th May 2010 20:41 UTC
Thread beginning with comment 427234
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: IE8 will be the next IE6
by apoclypse on Sun 30th May 2010 19:10
in reply to "RE[2]: IE8 will be the next IE6"
The issue is the flash runtime. It hard to get a consistent alternative flash runtime since the actual Adobe runtime is not documented and does a lot of things in the background that is not clearly understood, even with reverse engineering. The SWF format is very much an open spec and can be implemented by anyone, but the flash runtime is the real problem and is one of the main reasons we don't have any viable alternatives at the moment.
That demo is impressive and it ran really well in Safari on my machine. The issue s going to be older flash files, or more complex flash movies that have far more going on as well as sites with video.




Member since:
2005-07-06
HTML5 can implement Flash, but Flash can’t implement HTML5
Holy crap, that's incredible! Admittedly it has some audio sync issues but still!
My question is, if it's apparently so quick and easy to put together a Flash-to-HTML5 translator, why is it taking so long to put together a decent alternative Flash player? I can only guess the answer is that specs are easy to understand and translate, but actual rendering etc. is not so easy to implement...