Yes, it does. The issue was with a "pre-release" version of OS X, hence anyone claiming Adobe did not test on "pre-release" versions were dead wrong. Like I stated. No less, no more. Thanks for missing the point completely, something a developer of 16 years should have grasped, having a logical mind.![]()
Thanks for your selective quotation, but Adobe saying that they tested a pre-release Lion does not make it the truth -- anybody can lie or make excuses. Adobe making a statement does not prove or disprove anything except for the fact that they need somebody editing their statements before they make them public. Adobe may have worked very hard on Flash for Lion for all I know. My only beef is that their public statements do not make it look that way and only serve to make them look bad. I stand by that. You apparently missed my point entirely. But thanks for playing.
Google is much ahead of Apple for HTML5 pushing. Remove the blinders for a minute and look at who sits on the WhatWG and who's the editor of the very standard you claim Apple is pushing the most.
Also, look very closely at the HTML5 support in the shipping Chrome and shipping Safari browsers...
WebM does not go against HTML5. What are you talking about ? WebM is a patent royalty free standard codec at this point. H.264 is not. H.264 poses problems for people who'd want to implement HTML5 but not have the money to license H.264 to do it. WebM vs H.264 is essentially GIF vs PNG of the 90s. Except this time, PNG has corporate backers. WebM is very much about easing and broadening HTML5 adoption. H.264 aims to make HTML5 a corporate only affair.
I think you quite grossly misunderstand what HTML5 is. I'll stop here, obviously your grasp on HTML5 is very weak and this is completely off topic.
Rant more my friend, educate yourself less.
Educate myself? Please. You should remove your blinders and try to see the motives behind the actions of these companies. First off, what does H.264 liecnsing cost for a non-corporate entity? Have you looked it up? Have you educated yourself? The answer is nothing? That's right.... zero! To quote Ed Bott (something I am not often prone to do):
The amounts are charged annually and are based on the number of subscribers:
100,000 or fewer subscribers = no royalty
100,001 to 250,000 subscribers = $25,000
250,001 to 500,000 subscribers = $50,000
500,001 to 1,000,000 subscribers = $75,000
greater than 1,000,000 subscribers = $100,000
Do the math. If you have 350,000 subscribers, your annual royalty cost per subscriber is a little over 14 cents, or 1.2 cents per month. Not exactly exorbitant.
Mozilla foundation is hardly poor. They receive money from many corporations and users who support their work. If WebM was about what they say, then why remove H.264 support from Chrome? Why? It costs Google no additional money to include H.264 support in Chrome. However, if you have a website using Flash Video, then Flash Player includes H.264 support. So if I am running a Web site and I want my users to be able to access my videos in any browser, then I can either re-encode in WebM to get Chrome users, or I can embed the Flash player applet on my page so Chrome can use it without me re-encoding.
I fully grasp what HTML-5 is -- and it goes way beyond video. However, I feel that when it comes to "open web standards" Google only cares so long as something is a means to the end of driving more ads. They are no champion. You might want to stop strapping yourself into that Google high chair and letting them spoon feed you the creamed carrots. You're a big boy now, you can think for yourself. While your at it, you can stop taking everything Adobe says as fact as well.
Maybe you should change your handle to GullibleWRX?
That was a nice attempt at diversion to refuting my points though. Keep it up. And again, thanks for playing.
Last edited: