Announcement

Collapse
No announcement yet.

Opera To Release WebKit-Based Web Browser

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Opera To Release WebKit-Based Web Browser

    Phoronix: Opera To Release WebKit-Based Web Browser

    Next month Opera will be rolling out "Opera Ice", a new web-browser for smart-phones and tablets. This mobile Opera browser won't be built on their Presto engine but rather the popular WebKit engine. Initially this WebKit-browser is just targeting the mobile space but it's expected to eventually land on the desktop too...

    http://www.phoronix.com/vr.php?view=MTI3ODU

  • #2
    This is from the same people that said Facebook would 100% buy Opera a while ago. There is no press release from Opera so take it with a grain of salt.

    Comment


    • #3
      I really don't know what to make of this. I've been an Opera user for 13 years. I don't hate WebKit but I was under the impression they were very proud of their engine.

      Comment


      • #4
        Too bad their problems with dark themes are in the UI layer, not in the HTML rendering engine.

        Comment


        • #5
          im 10 year opera user and i think webkit engine might be a good idea.
          their presto engine is good and all that, but it just doesnt grow with new features fast enough.
          so i think switching to webkit will grant us, opera users, more rapid updates and features to keep up.

          lets wait and see.

          Comment


          • #6
            Originally posted by curaga View Post
            Too bad their problems with dark themes are in the UI layer, not in the HTML rendering engine.
            There's problems with both actually and it's the one thing I hate about Opera but I've managed to make it bearable.

            Comment


            • #7
              One less rendering engine is not good for web standards; especially in the mobile space, where people may already be tempted to target webkit instead of standards because of the Android/iPhone dominance.

              Comment


              • #8
                Originally posted by TheCycoONE View Post
                One less rendering engine is not good for web standards; especially in the mobile space, where people may already be tempted to target webkit instead of standards because of the Android/iPhone dominance.
                If you want to port a browser to iOS, WebKit is the only choice.
                Specifically the version of WebKit that Safari is using. That's what Firefox had to do.

                Comment


                • #9
                  Originally posted by who_me View Post
                  This is from the same people that said Facebook would 100% buy Opera a while ago. There is no press release from Opera so take it with a grain of salt.
                  ...a cup of salt

                  Comment


                  • #10
                    Indeed, loosing Opera's rendering engine on both desktop and mobile will be a big blow to web standards.
                    As much as webkit is cool, it is dangerous if it is "the one and only"...

                    Comment


                    • #11
                      Originally posted by intellivision View Post
                      If you want to port a browser to iOS, WebKit is the only choice.
                      Specifically the version of WebKit that Safari is using. That's what Firefox had to do.
                      Actually Opera Mini for iOS worked around the rules. It uses Opera's own engine, albeit, the rendering is done remotely.

                      Comment


                      • #12
                        It's a shame

                        I haven't used Opera much, but the switch to Webkit means that there are only three engines remaining- Gecko, Webkit, and whatever Microsoft is doing...

                        This isn't that great from security and compatibility perspective- less targets in case of security, and we'll soon see "this page is best viewed with Webkit" type of page design... Monopoly is always bad, and this will reduce competition. Although rate of innovation in web browsers today is quite good, so this probably won't have huge impact.

                        Comment


                        • #13
                          Webkit already is the new IE, at least in the mobile space. As funny as it may sound, Microsoft has major problems with it because so-called web developers often use CSS with only webkit prefixes, and don't bother with adding the prefixed versions for other vendors or the W3C standard variant of the property.

                          Comment


                          • #14
                            Monopoly

                            Originally posted by coder111 View Post
                            Monopoly is always bad, and this will reduce competition.
                            This will nearly be the first near-monopoly around an open-source product (beside Apache web server).

                            Open-source monopolies don't hurt innovation speed (it usually improves). It may cause more security runs, which forces vendors to speed-up their update processes. It ends "monopoly-owner tactics" like high prices or bundling-based monopoly growth. It can hurt standards development (because nobody cares anymore).

                            These people-owned monopolies are better for people.

                            Comment


                            • #15
                              It's not a problem

                              ...if they release Presto as GPLv3+. Else yes, the open web will suffer.

                              Comment

                              Working...
                              X