Language Selection

English French German Italian Portuguese Spanish

Chrome VS Midori

Filed under
Software

Both in response to my recent review of Midori and some argument... ehm, discussion, in yesterdays Ubuntuesday OMG! Podcast, I have taken on the task of running Midori and Google Chrome through a few tests to see which one performs better and faster in some basic web tasks. While, when I wrote my original review, I did a few 'eye ball' guessing tests, those were slightly less than... measurable. So, on to the tests! I'm running a Dell Studio XPS 13", with a 2.66 Ghz Core 2 Duo, 4 gigs of ram, and off of a wireless internet connection.

Cold start

I tried this test a few different ways. First, I set both Midori and Chrome to OMG!s homepage, and (with both set to resume session) opened them both by opening desktop shortcuts. Midori tended to open in 2 seconds or less, Chrome just a hair behind, but Chrome would load OMG! much quicker, usually within about 6 seconds, with Midori at about 12. Amusingly enough, however, Chrome crashed after my 5 try, and gave me one of those "Could not load your Profile" Errors. Awesome. Also amusing was the time that Midori loaded OMG! all the way before Chrome even showed up to the party. I then ran the same test, but with blank tabs.

rest here




More in Tux Machines

Ask Safia: How do I move from a proprietary software background into open source?

Your inexperience with open source tools definitely is not going to prevent you from participating in the open source community. Regardless of the closed nature of the platforms that you’ve worked with previously, you have all the skills needed to be a valuable open source contributor. If you’ve learned a thing or two about documentation, consider addressing documentation issues on projects. If you had experience in QA or testing, you can start off by user testing the software and identifying areas for improvement or for improving code coverage. Valuing your skill set and the nature of the environments that you have worked in is important. Read more

How Do You Support Your Distro?

I think of them as our own little personal supernovas. There’s a brilliant flash when a Linux distro tosses in the towel and calls it quits. But whenever a distro goes away, it leaves behind the people who’ve used and worked with it on a daily basis. While there’s no formation of a black hole, there is hole at the center of users’ work schedules and that disruption can do serious damage to those relying upon the distro’s stability. And while getting a new distro installed and running isn’t the nightmare it used to be, it’s still a pain. Read more

Rygel Open-Source Media Server Gets Hack to Support AVI Playback on Philips TVs

The open-source Rygel DLNA (Digital Living Network Alliance) media server software has been updated earlier, May 23, 2016, to stable version 0.30.3 and development build 0.31.1. Read more

GNOME News

  • GNOME.Asia Summit 2016
    This year summit held at Manav Rachna International University (MRIU), which is located in the Faridabad district Delhi, it’s a quiet, beautiful and very very hot place. It gave me a lot of wonderful memories.
  • Endless and Codethink team up for GNOME on ARM
    A couple of months ago Alberto Ruiz issued a Call to Arms here on planet GNOME. This was met with with an influx of eager contributions including a wide variety of server grade ARM hardware, rack space and sponsorship to help make GNOME on ARM a reality.
  • External Plugins in GNOME Software (5)
    There’s a lot of flexibility in the gnome-software plugin structure; a plugin can add custom applications and handle things like search and icon loading in a totally custom way. Most of the time you don’t care about how search is implemented or how icons are going to be loaded, and you can re-use a lot of the existing code in the appstream plugin. To do this you just save an AppStream-format XML file in either /usr/share/app-info/xmls/, /var/cache/app-info/xmls/ or ~/.local/share/app-info/xmls/. GNOME Software will immediately notice any new files, or changes to existing files as it has set up the various inotify watches.
  • External Plugins in GNOME Software (6)
    This is my last post about the gnome-software plugin structure. If you want more, join the mailing list and ask a question. If you’re not sure how something works then I’ve done a poor job on the docs, and I’m happy to explain as much as required.
  • Week 1 of May-August Outreachy
    The Outreachy internship requires that interns maintain a blog, writing at least every other week. This shouldn't be a problem for the usability project. For the first few weeks, I'll essentially give a research topic for Diana, Ciarrai and Renata to look into and write about on their blogs. I've structured the topics so that we'll build up to building our usability tests.