5 ms·
There will be licensing and royalty issues. When a big company in Redmond says stuff like this, its called FUD. This is FUD, plain and simple. What technolog
by kenjackson 16y ago
There will be licensing and royalty issues.
When a big company in Redmond says stuff like this, its called FUD. This is FUD, plain and simple.
What technologies have patents, fees and/or licensing around them?
H264, MP3, Flash, USB, Java, HDMI, CDMA, GSM, LTE, WiMax, Firewire, CD, DVD, BluRay, MP3, AMOLED, and many more.
To argue that computing is going to collapse with the existence of all these is pure FUD. Its FUD when MS does it. It's FUD when Google or the Google camp does it.
UPDATE: And I forgot a biggie, MPEG-2.
- tomlin 16y agoNot so fast. These licensed technologies you speak of are not embedded within web browser standards. It's a big difference. Flash, for one, is a plugin. It hitches a ride with the browser, it's not part of its standardized, internal workings. Google probably will benefit financially from this change and the rhetoric from Google's camp probably is FUD. No different than what Apple is doing with it's proprietary App Store process or it's closed source OS or how Apple's camp (again, I'm apart of this camp) manages to stick-shift through an uncomfortable conversation about open source beyond WebKit. The difference is that WebM might also help open source as well. Just because it benefits a corporation doesn't necessarily mean it's the devil.
- pohl 16y agoNot so fast. These licensed technologies you speak of are not embedded within web browser standards. ...which is puts them on equal footing with H.264 and WebM. The HTML5 video standard specification does not specify a codec, so no codec can be said to be "embedded within web browser standards" either.
- GHFigs 16y agoThese licensed technologies you speak of are not embedded within web browser standards. Neither are video codecs.
- rbanffy 16y agoAnd not embedding h.264 may prevent it from becoming a de-facto standard while pushing WebM, a fully open competitor (that's not perfect yet), may give it a chance of becoming, rightfully, part of a standard.
- kenjackson 16y agoThis was a spit in the face of Apple, and Jobs is the type to hold grudges. iOS devices won't use WebM. And no matter how you slice it, iOS devices will be popular in the formative years of HTML5. At best WebM splits <video> into a state where its really not much more useful than it is today. Or H264 just kills it anyways, and Chrome dies. In no case does WebM become the defacto standard.
- mitjak 16y agoSo, because of your questionable personal knowledge of Jobs and the influence he holds over Apple, a video codec will fail? Last time I checked the world didn't run entirely on Apple hardware and software alone.
- rbanffy 16y agoHaving a fragmented standard or no standard at all is usually better than having a very bad one. People can always encode to multiple file types if they want to serve the increasingly large audience that doesn't support h.264. And, BTW, Android phones just passed their iOS competitors, so, it doesn't matter how popular they will be, Android devices will be more popular. If Google decides they won't support h.264, it will be a serious hit.
- kenjackson 16y agoI agree with your thesis. I just disagree that H264 is a worse standard than WebM. On marketshare, while Android just passed up iPhone, something happened this past Tuesday which will probably tighten up the race a fair bit more. On top of that, the report counted iPhone subscriptions. Not iPad or iPod Touch devices. I've heard estimates that iPod Touch + iPad sales == iPhone sales. And iPad2 is likely hitting the market in a few months. In anycase the road we're going down is a fragmented one. Maybe people will get it right for HTML6. But I think most of the vendors at this point take the view that they'd rather have a fragmented web, rather than one dictated by their competitor.
- redial 16y agoHow is bundling flash any different than bundling H.264 in Chrome? none of those are part of the HTML5 specification. And in Chrome, flash is part of the internal workings. You can't update (or remove) the flash player inside.
- stanleydrew 16y agoI can tell you exactly how, as many others already have in this and other discussions: flash is a plugin; h.264 support is native browser code. Google bundles flash for one reason only: to make sure that users aren't given the chance to shoot themselves in the foot by not upgrading. Everyone downloads the flash plugin because sites require it. It has 98% penetration (perhaps less now with more people using iDevices, but still very high). But people never update the plugin, which is a major security issue. Google has solved that problem in chrome. And you are mistaken that flash is part of the internal workings of chrome. You can disable it: see about:plugins. And there is no need to update it since chrome takes care of that for you.
- antimatter15 16y agoNo. You can disable the internal flash plugin by navigating to about:plugins and hitting disable. It's not part of the internal workings.
- tomlin 16y agoTo those who pointed out that a codec is not a part of the browser standards, you are correct. I misspoke. I don't know why since I remember that Mozilla also took this stand a while back. Apologies. :)
- daleharvey 16y agoand none of those are required to produce or consume web based content. I dont need to pay anyone in order to write text on the web, I dont need to pay anyone in order to share images that I have created, I dont understand why people think its ok that we should have to pay to share the videos we create I know mpeg-la arent actually charging end users (yet), but that doesnt matter, someone has to pay
- recoiledsnake 16y ago>When a big company in Redmond says stuff like this, its called FUD. This is FUD, plain and simple. Even if they say the sky is blue? I don't even know why you're dragging MS into this. They've already stated that IE9 will pick up WebM codecs if they're installed on the machine and will use it play HTML5 video. They just don't want to ship it with the OS and step onto patent landmines which could cost them billions in lawyer and licensing costs. Google does not provide patent indemnity with WebM.
- kenjackson 16y agoI brought MS into it, not to bash MS, but to point out how hypocritical these arguments often are. If MS says something with no substantiation, but merely an attempt to create fear, uncertainty, and doubt in the future, people are up in arms yelling FUD. But when Google does it it's about the greater good of humanity.
- tomlin 16y agoYou could say the same for any tribe, I think. I like Google but I doubt that they are making decisions for the greater good intentionally, or all the time. I do think that Google, like Apple, try to swing their business model towards a better design or better implementation. In a lot of those cases, the better implementation or design is open source or built for the greater good.
- chc 16y agoIt's not Google making up FUD — Google is noting an objection that's been around for a long time, and they're doing something about it. Mozilla has been saying the same thing for a long time. And I don't know how you even create FUD about something like this, where the uncertainty is based on traps that are known to exist, which most users are currently standing on but simply haven't been triggered yet. Is it a controversial claim that H.264 requires a patent license? Is it a controversial claim that MPEG-LA has only offered a limited-time indemnity, and that only for a subset of uses? This is all verifiable and documented.
- 16y ago
- deleted 16y ago[deleted]