Linked by Thom Holwerda on Wed 18th Jul 2012 21:12 UTC
Windows The moment Microsoft announced it would lock other browsers out of being installed on Windows RT, we all knew regulatory bodies the world over were wringing their hands. Today, this has been confirmed: in the wake of an investigation into Microsoft not complying with the existing antitrust rulings regarding browser choice, the EU has also announced it's investigating Windows 8 x86 and Windows 8 RT (ARM).
Thread beginning with comment 527290
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by Drumhellar
by shmerl on Thu 19th Jul 2012 00:09 UTC in reply to "RE: Comment by Drumhellar"
shmerl
Member since:
2010-06-08

and I can't see how the situation is the same: even though iOS dominates the tablet, it is far from dominating the web


Well, that's easy to point out - codecs. Apple dominates the web with allowing usage of only MP3 and H.264 on their devices for web audio/video, and banning browsers that could allow using open codecs (Vorbis, Theora, VP8 and etc.). This way they indirectly push Web developers to use these closed codecs if they want to target Apple mobile devices (which are a big part of the market and can hardly be ignored).

Essentially Web publishers are forced to encode their content twice - in open codecs for normal browsers, and in closed codecs for mobile Safari (same story will be with Windows RT it seems). Encoding in closed codecs requires licensing if publishing has commercial purpose. Plus doubling hosting space costs money and less efficient closed codecs waste more energy, being bad for the environment. So in essence Apple does dominate the web with their ban on alternative browsers for iOS.

IE on mobile MS devices has the same issue. On the desktop, IE can be remedied with installing plugins to support open codecs, while on mobile devices with their crazy restrictions this is impossible.

Edited 2012-07-19 00:27 UTC

Reply Parent Score: 7

RE[3]: Comment by Drumhellar
by Fergy on Thu 19th Jul 2012 08:14 in reply to "RE[2]: Comment by Drumhellar"
Fergy Member since:
2006-04-10

Well, that's easy to point out - codecs. Apple dominates the web with allowing usage of only MP3 and H.264 on their devices for web audio/video, and banning browsers that could allow using open codecs (Vorbis, Theora, VP8 and etc.). This way they indirectly push Web developers to use these closed codecs if they want to target Apple mobile devices (which are a big part of the market and can hardly be ignored).

Agreed. On top of the stupid H.264 and mp3 requirements I also get more and more websites that want Chrome or IE for 'the best experience' or even to function. In that way Chrome has joined IE6.

Reply Parent Score: 2

RE[4]: Comment by Drumhellar
by zima on Tue 24th Jul 2012 00:08 in reply to "RE[3]: Comment by Drumhellar"
zima Member since:
2005-07-06

Firefox has joined IE like that much sooner, and it was overall much worse in the times of "IE or FF" - but with the wide adoption of Webkit (so also Chrome), which gives us at least three commonly used browser engine families, the web in general has become much more standards-compliant (which is particularly noticeable if you use some outsider - Opera, for example)

Reply Parent Score: 2

RE[3]: Comment by Drumhellar
by No it isnt on Thu 19th Jul 2012 10:33 in reply to "RE[2]: Comment by Drumhellar"
No it isnt Member since:
2005-11-14

Yes, that's what I feared as well, back when I thought there would be something in all the hype. But the iPad isn't taking over the web, it segments it into, well, web and apps. Giving iOS users a crippled web experience just encourages them to pay for "premium" app content.

Reply Parent Score: 5

RE[3]: Comment by Drumhellar
by zima on Wed 25th Jul 2012 23:48 in reply to "RE[2]: Comment by Drumhellar"
zima Member since:
2005-07-06

Apple dominates the web with allowing usage of only MP3 and H.264 [...] they indirectly push Web developers to use these closed codecs if they want to target Apple mobile devices [...]
less efficient closed codecs waste more energy, being bad for the environment

AAC more than MP3. And open codecs are a plenty nice enough concept that you don't have to make up issues with closed ones - perf is fine, they are actually usually best supported.

Overall, it's hardly only Apple, and not really too big long-term problem (especially with open codecs providing some pressure...) - big players behind most consumer toys are also the ones behind mpeg-la, they will protect it, the support will be there. That is the point, and why they will continue pushing it.

All new TV standards use h264 + aac (well, or a bit earlier mpeg standards, for now, if their particular variant was introduced a bit "too soon" in places), and none uses the likes of vp8. h264 will be the standard for most of the rest of your life, or all of it, accept it (which also means that its ~patents/closed issues on the web will go away relatively soon)

Reply Parent Score: 2