Opera joins in Jobs v Flash argument
in [Mac Systems]
|
Prev: Why html5/proprietary H.264 will fail (was) Scribd "scrappingFlash and betting the company on HTML5"
Next: Airport turns off on reboot
From: DevilsPGD on 6 May 2010 15:18 In message <Xns9D708B8384BEAnoonehomecom(a)74.209.131.13> Larry <noone(a)home.com> was claimed to have wrote: >Michelle Steiner <michelle(a)michelle.org> wrote in >news:michelle-6367C2.08010806052010(a)62-183-169-81.bb.dnainternet.fi: > >> but that the >> company needs to start embracing web standards if it doesn't want to >> come under constant attack. >> > >html5 support isn't the problem. It's the PROPRIETARY H.264 being allowed >to infect the net with html5 that's the problem. H.264 will, at some >point, be calling in the LICENSE FEES, or else. Or else will mean, >suddenly, an awful lot of the web content Steve Jobs' iTunes wants to get >rid of....their competition. I think H.264 will be the tool to accomplish >that for the big elephants in the room...Apple, Micro$oft, Google, etc. To me, if H.264 wants to win here it needs to start making the licenses perpetual and irrevocable. However, if they can get all the major players on board (which is very close to happening at this point) and spread just enough FUD about the opposition to keep it at bay then it's just a waiting game until H.264 becomes the standard.
From: Ian Gregory on 6 May 2010 16:04 On 2010-05-06, Larry <noone(a)home.com> wrote: > html5 support isn't the problem. It's the PROPRIETARY H.264 being > allowed to infect the net with html5 that's the problem. There are several problems with that statement. For a start, H.264 (unlike Flash) is not proprietary - it is an open standard. Unfortunately in countries where software patents are upheld vendors and commercial users are expected to pay patent licensing royalties for the patented technology so it does have its own problems. Secondly, it is not HTML5 which is allowing H.264 to "infect the net" - websites have been serving H.264 video using Flash for a while now, and of course millions of people are torrenting H.264 files. HTML5 makes it easy to serve Theora video for a totally open system but unfortunately that severely limits your audience. IE users are left out because IE does not support HTML5, Mac users are left out because Apple does not support Theora (though it might work if you install the Xiph.Org QuickTime component), and smartphone users are left out because Theora has not been implemented in hardware. If you use H.264 instead of Theora then you pick up the smartphone and Mac users, but IE users will still have to wait for IE9. On the other hand you loose Firefox users because Mozilla won't support H.264. Of course you can include both H.264 and Theora in an HTML5 video tag, but that means you have to encode everything twice, and there are concerns about submarine patents surfacing down the line and biting commercial users of Theora. The whole thing is a bit of a mess - but still preferable to the situation where you can't watch video on the web without using proprietary software from Adobe (which may well be serving H.264 anyway). Ian -- Ian Gregory http://www.zenatode.org.uk/
From: Your Name on 6 May 2010 17:02 "Michelle Steiner" <michelle(a)michelle.org> wrote in message news:michelle-EB8209.13173306052010(a)62-183-169-81.bb.dnainternet.fi... > In article <MPG.264d306ccabcf2d59896e9(a)news.individual.net>, > Jim Mason <jimandlinda(a)geemail.com> wrote: > > > Gawd. Please don't fall into the Loser Larry territory of using > > Wikipedia to attempt to bolster your arguments. It makes you look > > desperate, insecure and idiotic :-( > > It's not the source that does that to him; it's his failure to understand > what he's quoting. Except Wikipedia is full of idiots like him posting nonsense, lies and rumours as though it is true ... especially for upcoming / unreleased things. Wikipedia is a waste of server space, as is the similarly uncontrolled IMDB.com.
From: Your Name on 6 May 2010 17:04 "Ian Gregory" <ianji33(a)googlemail.com> wrote in message news:slrnhu6877.3no.ianji33(a)zenatode.org.uk... > On 2010-05-06, Larry <noone(a)home.com> wrote: > > > html5 support isn't the problem. It's the PROPRIETARY H.264 being > > allowed to infect the net with html5 that's the problem. > > There are several problems with that statement. <snip> Not to mention that Loser Larry has absolutely NO idea what he's talking about anyway.
From: Jolly Roger on 6 May 2010 18:07
In article <michelle-6201F5.12305906052010(a)62-183-169-81.bb.dnainternet.fi>, Michelle Steiner <michelle(a)michelle.org> wrote: > In article <jollyroger-4B5A49.11422206052010(a)news.individual.net>, > Jolly Roger <jollyroger(a)pobox.com> wrote: > > > > [Dunno how, but my post got mangled, at least it looked that way on my > > > server. Trying only once more, and my apologies if this doesn't fix > > > it] > > > > It looked fine both times here, though the initial post was in a > > different font on my screen, because you sent it with 8-bit UTF 16 > > encoding. I probably have MT-NewsWatcher set to use a different font for > > such posts. > > On my system, MT-NW displayed it in very small characters; I used the Edit > menu to decoded it as ISO - 9, which made the characters a readable size. > > The "offending" character, by the way, was an em-dash. Nice going, Michelle... : P -- Send responses to the relevant news group rather than email to me. E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR |