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 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.
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.
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.