Pre-Alpha Chrome browser for Linux available


Recommended Posts

Pre-Alpha Chrome browser for Linux available

post-88362-1237277950.jpg

Last week I found an Ubuntu package repository for the Chromium browser, the open source project behind Google’s Chrome browser. I didn’t get excited until I saw this post, which shows that the packages do contain a working web browser!

Chromium for Linux is pre-alpha software, but farther along in development than I expected. The GTK-based Linux interface looks and works just like Windows interface. The browser rendered sites I tested it with just fine, and I haven’t been able to crash the it yet. Lots of features, such as bookmarks, the options window, and even the about window, are simply are not implemented yet.

The big missing feature currently is the tab bar. You can open a new tab just fine, but the tab bar is missing so there’s no way to switch between tabs. Like the Windows version, Chromium for Linux runs each tab in its own process. Tab crash detection seems to not be implemented yet as killing a tab process causes the page to just stop responding.

Chromium, even in this early state, feels much faster than Firefox. I compared the 280Slides presentation editor running in Firefox 3 and Chromium, and the difference was like night and day. Chromium scores very well in the SunSpider Javascript benchmark: 4.7 times faster than Firefox 3, and 2.9 times faster than Firefox 3.1 Beta 3.

Firefox 3.1 Beta 3 1914.6ms +/- 6.2%

Firefox 3 3082.8ms +/- 0.2%

Midori 0.1.4 1111.4ms +/- 1.2%

Chromium 657.4ms +/- 2.6%

The Ubuntu Chromium Daily Builds PPA makes installing Chromium in Ubuntu very easy to do. However, these packages are pre-alpha and completely untested, they may not work for you at all. Follow the directions on the PPA page to add the software repository. Install Chromium from the package chromium-browser (click the link to install), or by running the command below in your terminal:

sudo apt-get install chromium-browser

The repository should be updated daily with the latest Chromium code. I’ll definitely be following Chromium for Linux’s development from now on.

souricon.gifTombuntu

souricon.gifLaunchpad

  • 2 weeks later...
  • 2 weeks later...

Bump.

Quoted from Ubuntuforums.org, will try it out myself in a few minutes.

Chromium now has working CLICKABLE tabs, new tab button, bookmarks bar, speed dial, ctrl+f dialogue, better font rendering, icognito browsing mode and i find it's by far the most stable build yet.

souricon.gifUbuntu Forums

  • 7 months later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • It is silly there is no simple way to check whether this profile has been activated. CFRs are normal, but trying to even hide the fact if it's on / off seems silly, especially for something so user-facing. Surely Microsoft is "proud" of their engineering efforts on this one and ought to display it somwhere in the GUI.
    • Many Linux distros are not known for excellent battery life, so I'm not sure that is the best example. A more apt example may be Apple, but Apple's CPUs are simply far more efficient than Intel & AMD at single-threaded tasks like these, so "boosting" is not as power-hungry and less heat-inducing. Not to mention Apple will hardly engage P-cores for basic UI tasks; they use a pretty complicated QoS scheme to only activate P-cores for more serious workloads like HTML / JS execution or decompression or application launch. Microsoft is (smartly) doing it for launch, but also for UI tasks, which is the more nonsensical part: why ... do Windows 11's UIs need modern CPUs to boost? It should load so quickly that there's not even time for the CPU to boost.
    • I've not seen any controlled testing and, judging by Microsoft's mentality, within a year, they'll have added so much more bloat, it'll undo any perceptible latency benefit and we'll have boosted the CPU clocks for nothing.
    • It depends: heat soak is a thing. Initially on cold boot-up, the heatsinks & heatpipes are at ambient temp. After heatsinks & heatpipes warm up (through normal usage), they don't immediately cool to ambient temp when the load goes away. So their baseline is higher and the trigger point for fans is much less stress. Add a few more CPU spikes → it's too hot to stay at the same fan RPM → fans get triggered to start up up much sooner / get triggered to ramp much more quickly.
    • Can LibreOffice just shut up and worry about themselves and stop comparing themselves? Do we see Microsoft complaining about euro office?
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      71
  • Tell a friend

    Love Neowin? Tell a friend!