Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Ubuntu Will Stick With Firefox Over Chromium For Now

  1. #1
    Join Date
    Jan 2007
    Posts
    15,126

    Default Ubuntu Will Stick With Firefox Over Chromium For Now

    Phoronix: Ubuntu Will Stick With Firefox Over Chromium For Now

    While Canonical engineers keep raising discussions about swapping Mozilla Firefox for Google's Chromium as the default web-browser for Ubuntu Linux, the 13.10 release will continue using Firefox by default...

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

  2. #2
    Join Date
    Mar 2013
    Posts
    22

    Default

    As a dedicated firefox user who finds chromium just a limited uncustomizable browser can only salute this decision, at least some are still sticking to good old firefox.

  3. #3
    Join Date
    Apr 2010
    Posts
    772

    Default

    What's the reason for this? I mean, it seems like every few months, we get another article about Ubuntu proposing to switch to Chromium, and yet again, it's not actually happening. What's the drive behind this constant push?

  4. #4
    Join Date
    Mar 2009
    Posts
    69

    Default

    Also, last time I checked, Ubuntu's notification system did not work with Chrome (there some extensions that should do it, but they just don't work). While I have nothing against Chrome and Chromium there is no reason for this switch and so potential problems.

  5. #5
    Join Date
    Dec 2010
    Posts
    1,177

    Default

    Quote Originally Posted by Delgarde View Post
    What's the reason for this? I mean, it seems like every few months, we get another article about Ubuntu proposing to switch to Chromium, and yet again, it's not actually happening. What's the drive behind this constant push?
    It was explained in one article. Ubuntu devs wanted to write a Qt wrapper for Chromium's rendering engine and use that in Ubuntu Phone (instead of QtWebKit) and for Ubuntu Desktop they wanted to use the same rendering engine.
    No idea if the wrapper project advanced in any way.

  6. #6
    Join Date
    Feb 2012
    Location
    Kingston, Jamaica
    Posts
    316

    Default

    Quote Originally Posted by Awesomeness View Post
    It was explained in one article. Ubuntu devs wanted to write a Qt wrapper for Chromium's rendering engine and use that in Ubuntu Phone (instead of QtWebKit) and for Ubuntu Desktop they wanted to use the same rendering engine.
    No idea if the wrapper project advanced in any way.
    There is no need for it anymore. Digia is creatine QWebEngine based on chromium to supersede QtWebkit. Canonical just needs to wait for them to complete it rather than creating their own.

  7. #7
    Join Date
    Apr 2013
    Posts
    36

    Default

    Quote Originally Posted by Awesomeness View Post
    It was explained in one article. Ubuntu devs wanted to write a Qt wrapper for Chromium's rendering engine and use that in Ubuntu Phone (instead of QtWebKit) and for Ubuntu Desktop they wanted to use the same rendering engine.
    No idea if the wrapper project advanced in any way.
    I read a couple of those articles but the connection wasn't clear to me. They're planning this wrapper (actually Canonical's post said they're considering forking a large part of WebKit/Blink, and making a wrapper for their fork) for Canonical and other people to build applications with limited web capabilities, right? Why does that affect the normal web browser? Chromium on Ubuntu wouldn't even be using Canonical's WebKit fork, it would be using Google's normal Blink version, which will be API-incompatible with Canonical's version. In fact Canonical said the reason they're doing their own Blink fork and Qt wrapper is because Google/Apple refuse to provide a stable API. That seems like a crazy reason to switch more stuff over to WebKit.

    Personally I don't get why many applications build in their own web browsers. If I click a link in Google Earth I want to read that link in Firefox. Why the hell would I want to surf Wikipedia in a globe application, which runs at half the speed and covers up my view of the actual globe until I close it?

  8. #8
    Join Date
    Apr 2012
    Posts
    118

    Default

    Firefox on mobile is quite good... can't that be used?

  9. #9
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    536

    Default

    Quote Originally Posted by qlum View Post
    As a dedicated firefox user who finds chromium just a limited uncustomizable browser can only salute this decision, at least some are still sticking to good old firefox.
    Indeed. As a very very old timer from the phoenix days, I've tried to switch to chrome/chromium -- I love the speed and the integrated translation system for pages -- but all the configs and settings and habits I've piled up on firefox over the years are not available, or are only extensions that leave a lot to be desired.

    Although for normal users, I'm a bit torn on which is better.

  10. #10
    Join Date
    Dec 2010
    Posts
    1,177

    Default

    Quote Originally Posted by jayrulez View Post
    There is no need for it anymore. Digia is creatine QWebEngine based on chromium to supersede QtWebkit. Canonical just needs to wait for them to complete it rather than creating their own.
    I didn't know that they now actually do that. I've read in a blog post about that as an experiment. Too bad we'll be required to swallow 100MB for Chromium dependencies because the Blink fork removed all those low level abstraction layers that makes integrating WebKit into various toolkits so easy.

    Simply basing QtWebKit on Apple's stable WebKit branch probably was just too pragmatic…

    Quote Originally Posted by Chaz View Post
    Why does that affect the normal web browser? Chromium on Ubuntu wouldn't even be using Canonical's WebKit fork, it would be using Google's normal Blink version, which will be API-incompatible with Canonical's version.
    The rendering engines would be closer nonetheless than Gecko and Blink.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •