Slashdot Mirror


Opera Picks Up Webkit Engine

New submitter nthitz writes "Opera has announced that they will be dropping their rendering engine Presto, in favor of Webkit. This knocks the number of major rendering engines down to three. Opera will also be adopting the Chromium V8 Javascript engine. The news coincides with their announcement of 300 million users. '300 million marks the first lap, but the race goes on,' says Lars Boilesen, CEO of Opera Software. 'On the final stretch up to 300 million users, we have experienced the fastest acceleration in user growth we have ever seen. Now, we are shifting into the next gear to claim a bigger piece of the pie in the smartphone market.'" They've already submitted patches to improve multi-column layouts even.

51 of 314 comments (clear)

  1. Re:Hopefully we can narrow this down to ONE by cpicon92 · · Score: 5, Insightful

    We don't need multiple rendering engines, we just need one standards compliant one

    Ideally, yes that's true. In practice, this would result in the one becoming a defacto standard, and whomever controls the one controls the standard. We are already kind of seeing this with WebKit. Competition is never a bad thing.

  2. Monoculture, here we come (again) by McDutchie · · Score: 3, Interesting

    This is bad news. Another step on the way to browser monoculture, with all the problems that can bring. Next thing Firefox will switch to Webkit and we'll have only Webkit browsers and IE left.

    1. Re:Monoculture, here we come (again) by Anonymous Coward · · Score: 2, Insightful

      It's the natural end point of any "free" market. I don't understand why people have such a hard time understanding this.

    2. Re:Monoculture, here we come (again) by Vintermann · · Score: 3, Interesting

      Since Opera's engines were closed source anyway, I don't see the diversity they provided as terribly valuable. If they open source the stuff they're abandoning now (as they definitively should), that will be far more valuable.

      --
      xkcd is not in the sudoers file. This incident will be reported.
    3. Re:Monoculture, here we come (again) by Bert64 · · Score: 4, Interesting

      A browser monoculture based on webkit is at least better than a monoculture based on a closed source rendering engine...
      Just how bad it is, really comes down to who controls it and how much input other people have into it.

      Of course without intervention pretty much everything will end up heading towards a monoculture... Linux for instance has pretty much killed the varied proprietary unixes that existed just as x86 has killed the risc processors they ran on.

      So if a monoculture is inevitable, then minimising the damage by keeping it open is the best you can hope for.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    4. Re:Monoculture, here we come (again) by Anonymous Coward · · Score: 3, Informative

      Why this will never happen: http://browserfame.com/363/why-mozilla-gecko-will-not-adopt-webkit

    5. Re:Monoculture, here we come (again) by aaaaaaargh! · · Score: 2

      It's no big deal. If some monopolist messed around with a single platform it would be easy to replace html with an ad hoc markup language, make a browser for that and ignore all previous standards. I'm not joking. There is really nothing magic about document markup and "mobile" application frameworks, almost any undergraduate CS student could come up with something better than what we have now, and an alternative WWW would be adopted very swifty if the old one for some reason became inconvenient to most users.

      To give the doubters an example, I'm pretty sure that I could come up with my own SXML-based version of the web with embedded sandboxed, just-in-time compiled scripting language and my own fast browser within a few days or weeks at maximum, just by using existing HTTP(S) for the clients/servers and gluing together some existing Racket libraries. And I haven't even studied CS. I'm sure some smarter people could come up with something better and faster in even less time. Of course, as long as there is no pressing need, this would be quite a futile exercise.

    6. Re:Monoculture, here we come (again) by Peter+Bortas · · Score: 4, Interesting

      Operas code is quite clean. Way easier to read and understand than Firefox's. Don't know how it compares to Webkit code-wise.

    7. Re:Monoculture, here we come (again) by Sockatume · · Score: 2

      The open source community builds a tool that's so good everone adopts it? Unacceptable!

      --
      No kidding!!! What do you say at this point?
    8. Re:Monoculture, here we come (again) by McDutchie · · Score: 2

      What? There is no TCP/IP monoculture. There are many different TCP/IP implementations. All of them interoperate without problems because there is a well-defined standard. That is not monoculture, that is standardization. They are fundamentally different things.

    9. Re:Monoculture, here we come (again) by foniksonik · · Score: 2

      That wasn't a good answer. He basically just said that they've tied the browser UI to the render engine and don't want to separate the two. There's no reason they couldn't keep Gecko to handle XUL and keep their JS extensions to support the browser UI. They just don't want to. Add in the comment about WebKit not supporting new JS standards, which has nothing to do with WebKit (WebKit isn't a JS engine) and you're left wondering what the guy is trying to defend.

      --
      A fool throws a stone into a well and a thousand sages can not remove it.
    10. Re:Monoculture, here we come (again) by Peter+Bortas · · Score: 2

      Because I've read it.

    11. Re:Monoculture, here we come (again) by A+Friendly+Troll · · Score: 2

      This is bad news. Another step on the way to browser monoculture, with all the problems that can bring.

      From TFA:

      "It was always a goal to be compatible with the real web while also supporting and promoting open standards. That turns out to be a bit of a challenge when you are faced with a web that is not as open as one might have wanted."

      The web isn't open. It never was. Many, many sites only start working properly in Opera when you mask as IE/Firefox, because browser sniffing is still a thing even in 2013.

      The popularity of Webkit also brought its share of problems. Too many blogs and sites raving about experimental features, which end up being used on production sites with no fallbacks.

      The majority of Opera users won't care. The rendering engine is highly insignificant; people use Opera because of what the browser as a whole can do. I find it mind-boggling that you still need *extensions* in other browsers for something as basic as mouse gestures. I also have no idea how you can remap keys in Firefox or Chrome. Perhaps an extension as well for something as simple as that? Don't even get me started on UI customization; there's nothing that comes even close to what Opera can do.

      Opera was and still is great at innovating. Many "standard" features like tab reordering, speed dials and even ad blocking (!) appeared in Opera first, sometimes half a decade before someone else implemented it. If adopting Webkit means they can spend more time doing that, and if the "Opera experience" still remains, I'm fine with it and couldn't care less.

      By the way - Opera's been losing market share to Chrome in countries where it was most popular (former USSR). Now there's no reason for those who switched to continue using Chrome. They can return back to Opera.

      What still needs to be explained is what happens to all the embedded systems running Opera. That includes fridges, vending machines, airplane multimedia systems, and even the Wii.

  3. Can we have the source, please? by Dr.+Spork · · Score: 5, Insightful

    The Presto rendering engine had some pretty decent performance, and was often the fastest among the graphical browsers. If it's being abandoned, wouldn't it be nice if it were made available as open source? Webkit isn't the right tool for every occasion. I hate to see something so good just die.

    1. Re:Can we have the source, please? by The+MAZZTer · · Score: 2

      I can confirm that Opera was the fastest browser before Chrome was on the scene. I visited my aunt once and was trying to use her ancient PC with my thumb drive... Firefox took forever to start, but Opera was instant and browsing was nice and snappy.

      Still nothing compared to how Chrome would perform later, at least on other PCs, but still.

  4. Cost related? by Tridus · · Score: 5, Interesting

    Just speculation, but I wonder if this is cost related. It can't be cheap to keep Presto up to par with Webkit and Gecko. Using Webkit instead means they can spend less money on that, and devote more to the UI without particularly affecting the browser's standards compliance.

    So in that sense it seems like a sound business decision.

    --
    -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
    1. Re:Cost related? by thoth · · Score: 2

      That's exactly what the first link says is the reason:

      it [maintaining Presto] ends up taking up a lot of resources - resources that could have been spent on innovation and polish instead

      and

      Not only will it [switching to Webkit] free up significant engineering resources at Opera and allow us to do more innovation instead of constantly trying to adapt to the web

  5. Re:What do they consider a user? by SJHillman · · Score: 5, Informative

    Don't forget that Opera is more that just a desktop browser. It really shines on mobile platforms with Opera Mini and Opera Mobile. The Wii's web browser is also Opera.

    From what I hear, they're really big in second and third world countries where bandwidth is more limited and/or you pay by the kilobyte. Opera excels at compressing the content (especially with Opera Turbo).

  6. Re:So... why use Opera? by SJHillman · · Score: 5, Informative

    Maybe because of features other than the rendering engine? I prefer Opera's UI, but it's also great to use as a general web client with integrated email, IRC, torrents, etc.

  7. Makes sense... by dejanc · · Score: 4, Interesting

    As a web developer, I should be happy about this development, but the fact is: Opera was always standards compliant and as a user I liked how it rendered pages (qucikly and without any white screen gaps between page loads).

    But it probably makes sense for them. Webkit is solid and their costs will probably go down dramatically.

  8. Re:How much of this is down to crApple... by SJHillman · · Score: 2

    Opera was the first alternative browser available on iOS as a result of Opera Mini being classified as a "remote content viewer" rather than a browser.

  9. Re:So... why use Opera? by beelsebob · · Score: 2

    Well, because of all the other features. The rendering engine was never a reason to choose opera over them in the first place – it was much slower, especially the javascript engine.

  10. Re:What do they consider a user? by tibit · · Score: 3, Insightful

    Sorry, there no such thing as "excelling" at compression "especially" with Opera Turbo. The browser has zero control over compression, it can request plain old gzip compression from the server, and the server may or may not oblige. That's all that's available without a dedicated server. Opera Turbo is a system where the browser basically hijacks you connection and routes it over an Opera-controlled server. It's that server that then obtains the website content for you and compresses it. It's the only way technically to accomplish that, at the price of essentially giving yourself a man-in-the-middle attack. It's not very funny. The only thing their browser is really excellent at is IIRC browsing porn or generally image galleries with lots of image content. They were excellent at it even in their humble beginning days, where it was ad sponsored free or ad-free paid for -- you basically needed Opera to browse porn over a modem connection on a low-end machine (486DX2 w/Windows 95). With the switch to webkit, they lose whatever technical advantages they might have had.

    --
    A successful API design takes a mixture of software design and pedagogy.
  11. Re:Hopefully we can narrow this down to ONE by Anonymous Coward · · Score: 3, Insightful

    The point is, when implementations are free, why do we need paper standards at all?

    A standards organization is made up of industry members who are stakeholders and other interested parties. It's a democracy, which is why standards are always so slow in coming. An implementation is necessarily owned and managed by a much smaller group; democracy-styled software development management doesn't work.

    The system we have now where we have standards organizations which are sufficiently careful and methodical and multiple implementations with one or more also acting as testbeds is serving us well. It just happens that WebKit an implementation with many benefits and so is eating the lunches of the others, but let's not jump to the false conclusion that a single open-or-otherwise implementation would serve us just as well.

  12. Re:Why? by SJHillman · · Score: 3, Informative

    Everything other than the rendering engine? That's what really set Opera apart. The email client is really nice and the IRC and torrent clients aren't bad. I also prefer the UI to Chrome.

  13. Re:Opera by MarkGriz · · Score: 4, Funny

    Drama queen

    Not Oprah.... OP-ER-A

    --
    Beauty is in the eye of the beerholder.
  14. Re:Monoculture by LO0G · · Score: 4, Insightful

    How exactly does this work? If we had a monoculture (like we had with IE6), people code to the monoculture, standards be damned. If WebKit implements a standard badly, no amount of complaining by Microsoft and Mozilla will cause the WebKit folks to change their browser rendering to be compliant. And just like what happened with IE6, web developers will ignore the standard in favor of the WebKit implementation. We're ALREADY seeing this happen - webkit has sufficient market share that sites don't bother building standards compliant version of their mobile site, they just write for webkit and consider their work done.

    History has shown that if you have a monoculture, standards are irrelevant - the only thing that matters is the one implementation.

  15. Re:So... why use Opera? by SJHillman · · Score: 2

    Opera integrates the different components much more tightly than, say, Thunderbird and Firefox. Email and IRC effectively become just another tab and it allows them to share resources so that they're more efficient than having separate programs for each one. It'd be great if Opera released a light version with just the browser, but I don't think you'd really see huge improvements by removing those features simply because they are so well integrated.

  16. Re:What do they consider a user? by xaxa · · Score: 5, Insightful

    Sorry, there no such thing as "excelling" at compression "especially" with Opera Turbo. The browser has zero control over compression, it can request plain old gzip compression from the server, and the server may or may not oblige. That's all that's available without a dedicated server. Opera Turbo is a system where the browser basically hijacks you connection and routes it over an Opera-controlled server.

    So the first part of your comment was irrelevant, except to note in passing that Opera has always had good HTTP compression support, and other features to speed up page loading (e.g. not loading images, or loading them selectively).

    It's hardly hijacking if they they tell you what they're doing, and you have to click a button to enable it:
    When Opera Turbo is enabled, webpages are compressed via Opera's servers so that they use much less data than the originals. This means that there is less to download, so you can see your webpages more quickly.

    Enabling Opera Turbo is as simple as clicking the Opera Turbo icon at the bottom-left of the Opera browser window. When you are on a fast connection again and Opera Turbo is not needed, the Opera browser will automatically disable it.
    http://www.opera.com/browser/turbo/

  17. Re:So... why use Opera? by teg · · Score: 2

    Why would someone use anything other than Chrome or Chromium on any platform?

    On Mac, one good reason would be because it is just 32 bit - unlike the rest of the system. This means that e.g. java does not work in Chrome on Mac. While that might be seen as a good thing at some times ;), this means that you can't use many of the banks here in Norway - or do online credit card payments.

    Also, some might think that Google knows enough about you already...

  18. Re:Hopefully we can narrow this down to ONE by Richard_at_work · · Score: 4, Informative

    Who owns the master branch? Who guards the commit gates from the hordes? There's your defacto controllers of WebKit - you can fork all you want, but you need to get the main users (the browser integrators, Google et al) to follow your branch rather than the master.

    Apple owns the master branch.

  19. Re:What do they consider a user? by RedHackTea · · Score: 4, Informative

    For me, it's the best of Chrome (look, speed, good tabs, etc.) and Firefox (has about:config, intuitive, etc.). One thing that hasn't been copied from Opera yet that doesn't make any sense... Anytime you get a JavaScript alert box, Opera adds a little checkbox allowing you to stop executing scripts on the page. Ever accidentally land on a website that kept spewing off alerts without you being able to close the page except by killing it? Opera also did extensions right; they're super easy to make. Opera has always either been the first or the first to do it right. Hands down.

    --
    The G
  20. Re:Hopefully we can narrow this down to ONE by silviuc · · Score: 4, Insightful

    Their control is accepted by all developers, if indeed that is the case. The minute they turn rotten, is the minute they lose "control". See the OpenOffice - > LibreOffice case.

  21. Re:What do they consider a user? by v1 · · Score: 5, Insightful

    pera Turbo is a system where the browser basically hijacks you connection and routes it over an Opera-controlled server. It's that server that then obtains the website content for you and compresses it. It's the only way technically to accomplish that, at the price of essentially giving yourself a man-in-the-middle attack. It's not very funny

    And when you live in a small village in africa and an hour of smartphone use could cost a day's pay, you get mighty thankful for that compression. These aren't the sorts of people that do online banking and are worried about MitM. Many of them are very happy to exchange email with friends and relatives in another village, and text compresses very nicely.

    Just because it's not the right feature for you doesn't mean there isn't a significant sized group that really appreciates it.

    --
    I work for the Department of Redundancy Department.
  22. Re:What do they consider a user? by Anonymous Coward · · Score: 2, Informative

    The Wii's browser is god-awful. Probably why Nintendo switched to webkit for the 3DS and Wii U browsers.

  23. And the winner is... Mozilla?!! by Matthew+Raymond · · Score: 4, Insightful

    The W3C requires at least two implementations of a standard before it can become a Recommendation. Thus, Google needs at least one ally with its own independent browser implementation to push standards through to Recommendation status. Of the five major browser vendors (Microsoft, Google, Apple, Mozilla and Opera), three of them (Google, Apple and Opera) are now all using a single rendering engine: Webkit. Apple may have a separate JavaScript engine, but it's a fierce competitor of Google, as is Microsoft. This leaves only Opera and Mozilla as potential standards partners, and Opera just went Webkit/V8. So, basically, Mozilla becomes Google's de facto ally for Web standards. (As if they weren't already, considering WebRTC.)

    Congratulations, Mozilla. Your continued Google funding is assured.

  24. Re:Why? by DragonWriter · · Score: 2

    ow that they've switched to webkit, can anybody tell me what makes them different from Chrome now?

    Everything other than the rendering engine?

    Well, not everything, since they are switching to V8 Javascript engine, as well.

    OTOH, differentiation on lots of axes may not be as important to them as being able to drive the web in the direction they want. Opera-pushed changes to web standards may be easier get accepted by other browser vendors (and, consequently, standards bodies on which those vendors sit) if, when Opera pays the cost to develop their implementation, they've already automatically got patches to WebKit to implement them -- plus, Opera doesn't have to expend as much effort reimplementing new and widely used features from other vendors if they can just pull them in from upstream.

    Working from a common open source base means that each vendor can focus on what they want to do that is new rather than duplicating other vendors' work.

  25. Re:What do they consider a user? by Jappus · · Score: 2

    Glad to be of help:

    https://addons.opera.com/en-gb/search/?query=adblock

    Sometimes, things can be so easy. :)

  26. Re:Javascript?? Please, NO! by JustOK · · Score: 2

    Oh, like sanscript isn't a language to model sand casting?

    --
    rewriting history since 2109
  27. Re:What do they consider a user? by eennaarbrak · · Score: 3, Insightful

    The only thing their browser is really excellent at is IIRC browsing porn or generally image galleries with lots of image content.

    BS. I have a limited data plan, and I use Opera to reduce the amount of $$$ I pay. And it works extremely well. So what if my data routes through a server? It goes through various central points anyway. I know Opera can see my surfing habits, and adapt my surfing behaviour accordingly.

    Privacy is important, but it is ridiculous to assert that it is the only thing to take into consideration.

  28. Re:What do they consider a user? by Anonymous Coward · · Score: 3, Informative

    Yeah, opera has a lot of builtin features that are great for porn browsing. (like finding the next/previous image based on a number in the url). I ran into an Opera engineer at a live sex show in Amsterdam a few years ago and he confirmed that porn was their original demographic -- use IE for regular browsing, opera for the stuff you don't want your wife/husband/kids to know about. (And porn ads were the most lucrative.) They used to have work orgies and such but that's tamed down now.

  29. Re:What do they consider a user? by Mattcelt · · Score: 4, Informative

    Opera has always either been the first or the first to do it right. Hands down.

    You're not kidding. Opera's Multi-Document Interface (MDI) was the first foray into tabbed browsing nearly three years before anyone else.

  30. Re:Hopefully we can narrow this down to ONE by JDG1980 · · Score: 2

    Ideally, yes that's true. In practice, this would result in the one becoming a defacto standard, and whomever controls the one controls the standard. We are already kind of seeing this with WebKit.

    It's true that WebKit is becoming a de facto standard, but I don't really see this as a problem. Some people say it's just like what happened with IE6, but there are several reasons why that was much more problematic:

    • IE6 was a poorly-documented, closed-source implementation.
    • It was controlled by one company. Everyone else was frozen out.
    • It only ran on one platform.
    • Microsoft actually had an incentive to not make IE too good, because they saw Web-based applications as a strategic threat to their Windows business.

    WebKit doesn't have any of these problems. It's a free, open-source rendering engine that can and does run on just about any modern computing platform. Even though the official source tree is curated by Apple, there is major buy-in from other stakeholders including Google and Adobe, and any attempt by Apple to freeze others out would almost certainly result in a swift fork (just as happened with OpenOffice.org after the Oracle acquisition). The decade-long stagnation of the Web under the reign of IE6 was the result of a lot of very specific circumstances; it can't be replicated again, and certainly not with WebKit.

  31. Their rendering what? by wonkey_monkey · · Score: 2

    Opera has announced that they will be dropping their rendering ending

    I'd say something like "are the editors even trying any more?" if it hadn't been so clear for so long that no, they're not.

    They've already submitted patches to improve multi-column layouts even.

    Oy vey, what is dis, submit like an old Jewish man day?

    --
    systemd is Roko's Basilisk.
  32. Good news! by sidragon.net · · Score: 3

    Consider the goal: invariably produce specific output for specific input. Given certain markup, styles, and scripts, there's an expected result, and that result should be the same across all browsers. That's is why we have standards. Those standards help make the Web a great platform.

    What, then, is the purpose of WebKit, Gecko, Presto, and Trident—four modern browser engines—all consuming development resources, each in pursuit of the exact same standards? If each were successful, we'd have four completely duplicative pieces of software when we only need exactly one.

    Some people here are claiming about monoculture. Well, sorry, these aren't biological organisms. Imagine if, instead of having resources divided four ways, those resources were focused on a single project (or, at least, some of those resources were contributing to projects that aren't waste heat). These products are nearly as complex as operating systems. Think about what could be accomplished with all that poorly allocated effort?

    Now Opera have come in and helped illustrate my point. They finally realized it's inefficient for them to reinvent the wheel a fourth time. (Maybe Microsoft will do the same.) They may have also realized all this redundant effort also create unnecessary work for web developers, who must perform grueling work and testing to understand and react to the subtle differences in all these engines. With this decision, they can get their engineering talent to focus on useful development, and they've saved the rest of us quite a bit of time, too.

  33. Re:So... why use Opera? by Archenoth · · Score: 5, Informative

    I use Opera because it both has the best usage paradigm for me and integrates with pretty much everything I need to do online.

    It takes far less time for me to do anything in Opera than it would in another browser. There are extensions for some Opera features in other browsers, like Mouse Gestures, user scripts, and user CSS. But they all lack capabilities that Opera's native version has. There are also no extensions for some Opera features like Tab stacking, or mass-refreshing, pinning, or deleting tabs and windows. (Complete with incremental tab search.) The website-independent settings settings are also awesome, I've used them to make my Slashdot hot pink for example. :)

    Also, If I don't like Opera's interface... I can build it.

    It has shortcuts for everything too, and if it doesn't, you can make them. One in particular I use is Mousewheel tab switching. Firefox has partial mousewheel tab-switching in it's current incarnations, but it only works with [Right Click] + [Mousewheel down].

    Also I've seen mouse gesture extensions for other browsers, (The best extension is All-in-one gestures for Firefox since it also integrates Rocker Navigation.) but they don't encompass the entire browser and only web pages. So I can't use mouse gestures to close or navigate a settings menu for example.

    It's sidebar is also really useful. I use it for things like controlling VLC, or E-Mail and RSS and Usenet, or looking at Opera's CPU usage, or contact management with incremental search an everything (No screenshot for this one because too much personal information), or controlling Transmission (Torrent program), or interacting with notes, or quickly turning on/off my proxies or masking my user agent, or managing my tabs and windows, or

    Also, as a web developer... Opera has a lot of spiffy development features that lack in other browsers. Dragonfly has more capabilities than the Webkit inspector, for example it can inspect attached events in DOM nodes. There are also view modes built in that allow you to highlight element borders for debugging CSS or see DOM attributes inline. Autoreferesh is also good for debugging CSS and for repeating YouTube videos. :)

    I glazed over most of it's features, and it's still many magnitudes more functional than other browsers.

    How many extensions do you think I use to get this functionality? The correct answer is zero. And the browser takes up less space than either Firefox or Chrome when installed.

    Is this a good enough reason to use Opera?

    --
    The arch foe.
  34. Re:Hopefully we can narrow this down to ONE by dingen · · Score: 2

    No. Apple forked KDE's KHTML into WebKit.

    --
    Pretty good is actually pretty bad.
  35. Re:What do they consider a user? by RocketRabbit · · Score: 2

    I was using tabbed browsing in OmniWeb before Opera ever came out.

  36. Re:What do they consider a user? by hairyfeet · · Score: 2

    Small village in Africa? How about many areas of the USA that can't get anything but dialup or a capped all to fuck connection? At my mom's place the ONLY thing they can get is wiFi run by a Billy Joe Bob that knows jack shit about dividing bandwidth so when some dumbshit is watching netflix on the thing you pretty much have to have something like turbo.

    Most folks don't realize how truly shitty our coverage really is because they go by zip code and the way they measure is if ANYBODY in that zip code can get high speed? then they think anybody can.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  37. Re:What do they consider a user? by hairyfeet · · Score: 3, Insightful

    Sadly they've let it go to shit the past several releases, probably because they knew they were walking away from it. my oldest was a die HARD Opera user, he wouldn't touch a system without Opera and used to carry Opera portable on a stick so he wouldn't have to use anything else but even he is trying various browsers because he says Opera gets slower and buggier with each release.

    If they are gonna abandon presto I really wish they'd open up the code, who knows what good could be made of an open presto engine. After all Mozilla rose from the ashes of netscape, maybe with it open devs could make presto so good opera would end up switching back.

    Of course all this is ignoring the rotting elephant in the room which the EU and DoJ really REALLY needs to investigate, and that is Apple's ability to influence the market with their monopolistic practices. Before some Applelite chimes in with "Apple isn't a monopoly" bullshit, total bullshit, look up the wording. it says you do NOT need 100% of the market, you don't even have to own the majority of the market, just that you have the power to assert undue influence and you would be hard pressed to find anybody that says Apple doesn't seriously influence the markets. From the prices of books to whether the web will run on an open format like Theora VS a locked down H.264 ALL of the major calls about the web made in the last couple of years has been made with iPhone in mind.

    Do you think Opera would be ditching presto if it could run on the iPhone? Do you think we'd be forced to run HTML V5 before its ready or use a patent troll format like H.264 if iPhone users could choose between that and Flash and WebM and Drac and Theora? No if the company of St Steve of Cupertino says "it is thus" then that is what it is gonna be, no choices in the matter. And I think they need to be investigated as NO company should have that power, I was against MSFT using IE to gain control and I'm against Apple using iPhone/iPad to gain more control. No matter what device or OS you use the web should be about choice, not some corp laying down the law.

    --
    ACs don't waste your time replying, your posts are never seen by me.