Slashdot Mirror
A Mixed Review For Google Chrome On Linux
omlx contributes this link to LinuxCrunch's short review of Google Chrome on Linux, writing: "The summary of it is that although Google Chrome is in a beta stage, it is fast, stable, and has a simple, clean, and effective GUI design. On other side, Google Chrome has a small number of extensions, doesn't support RSS, lacks integration with KDE, and doesn't support complex scripts very well. Personally, I didn't succeed in using Flash Player on Google Chrome beta 1 (I am using OpenSUSE 11.2) and I wonder how the quality of Google Chrome OS will be, especially if it's based on Linux and Google Chrome."
Personally, I disagree. Flash works flawlessly on chrome. More features can be added later, you have to remember it is a beta. finally, as a person who had compiled Chrome OS, It works great. My only problem with it is lack of wireless card support, but once again BETA.
I've been using a mix of chrome and chromium on linux now as my primary browser for the last six months. I'm surprised at how stable it actually is (especially now). When I first started using it, the chromium builds weren't integrated into the UI very well, and were very finicky (especially with plugins). Now though, I've had zero crashes with the latest build (4.0.266.0) that I'm using. Flash works great under Ubuntu 9.04 with chrome, the dom inspector is up and running, networking options are now available (an improvement from the previous chromium build I was using), complex scripts (hebrew, arabic, etc) are working, and UI is operating exactly how you'd expect it to. Oddly enough, the only problem I'm having with it, is if the width of a text input box goes larger than around 600 pixels, I can't select the text outside of that 600px with my mouse (not that it's a problem, I just click elsewhere and use my lovely keyboard to get me where I need to be). Other than that, zero problems. Very happy with it.
I'm running Chrome in Ubuntu under Gnome and Compiz, I have Adobe's flash installed from restricted and swfdec removed (was blocking Adobe's) and all the extensions I've tried work: Feedly, Chromed Bird, Adblock, and so on. The only thing I notice about Flash (it even plays video fine!) is that sometimes input events such as clicking on a button in a flash element will "fall through" and not do anything. Annoying when your trying to select another YouTube video after the current one has finished playing. Overall though, my opinion is that it is already in an excellent state and can only get better from here: in active development.
Shh.
I had two systems, both 64-bit Fedora, that I tried Chrome on. On one, Flash worked fine from the moment I installed Chrome. On the other, Chrome didn't even notice the plugin existed. Flash (32-bit, wrapped with mozilla-plugin-config) worked just fine in Firefox on both computers. When I compared the two systems, it turned out that one was missing a symbolic link. The file is in /usr/lib64/mozilla/plugins-wrapped, but Chrome was looking in /usr/lib/mozilla/plugins.
Adding a symbolic link solved it.
More info: Getting Flash to work on Google Chrome for 64-bit Linux.
The entire Chrome application is open under a BSD license. You can check out the licenses of the dependencies as well here:
http://code.google.com/chromium/terms.html
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
As far as the KDE thing, though, I agree. Exactly what sort of "integration" with KDE was expected?
I would appreciate it if Chrome took it's default font size/color from the KDE settings. What would even be better is if there was a KDE theme that also took over the KDE look and feel for the browser window and the tabs, and the buttons and dialogues that Chrome has.
It not only has tons of extensions, (all the basics included, like Ad Blocking, Gmail Checker, etc) but has a fantastic way to search for them... on par with Mozillas plug-in search.
I agree, if I even bothered to RTFA, I would have stopped reading at that point.
Uhm, if you have a criminally broken router and feel no urge to work around it, you should disable IPv6 system-wide. No program should deal with such type of configuration on its own.
And your configuration seems broken: if you don't have any IPv6 addresses better than link-local, glibc shouldn't even send AAAA queries, at least in any semi-recent version. If you have any better addresses (not necessarily globally routable), the queries will be sent but since they go exactly the same way A queries go, there's no way for A responses to come swiftly but AAAA having to timeout, save for something on the way sabotaging them and dropping them silently. And since you claim that this happens for every access, it's something near you.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
It already does. On first boot XUL / JS is parsed into objects which are serialized as prototypes into XUL.mfl where mfl stands for Mozilla Fast Load. The next time the app starts it constructs the prototypes from the fast load file rather than the XML. The mfl file is regenerated when the XUL changes of course.