Hacker News Reader

Comment by adnymarc | Hacker News Reader

And still no full release version for Mac / Linux. I find this particularly interesting considering the Google "Operating System" is going to be a custom interface on top of a Linux kernel.

View on HN

I've been using the Linux version for several month now and honestly cannot tell the difference between it and the windows version. Just as stable, just as fast, and flash works without any problems. I'm guessing there is a good reason why they're not comfortable releasing it yet, but as an end user I haven't run across that reason.

Chrome for Mac is similar. Firefox is my main browser, but I give Chrome a whirl once a week or so and have yet to notice any deficiencies.

Well, one obvious deficiency is the lack of integration with password managers. That's deal-breaker for me.

Printing doesn't work on OS X or on Linux yet either.

What is this "printing" of which you speak?

I use SuperGenPass, which is just a js bookmarklet... It works equally well on Firefox, Safari, Mobile Safari, and Chrome.

http://supergenpass.com/

I'm running Chromium on Ubuntu x86_64, and I've yet to get Flash to work with anything other than YouTube.

How did you do that? I have zero flash. (I'm on x86_32 though).

I have --enable-plugins turned on atm and I don't see any difference between chromium's flash and firefox's, except that when the plugin crashes on chromium, I reload the page instead of the entire browser.

It depends on whether you're using the chromium-daily PPA or you used Google's deb (the former looks for Firefox's libflashplayer.so, the latter needs you to install it).

If you're using the chromium-daily PPA (https://launchpad.net/~chromium-daily/+archive/ppa), Chromium will look in a bunch of folders[1] for plugins, including ~/.mozilla/plugins. I suggest you get the tarball from http://get.adobe.com/flashplayer/ and put its libflashplayer.so in ~/.mozilla/plugins. Chromium will look here for it upon startup and you're set.

If you installed using Google's deb (http://dev.chromium.org/getting-involved/dev-channel), it doesn't yet search the Mozilla plugin dirs, and thus you need to make an /opt/google/chrome/plugins dir and put the libflashplayer.so in there and it'll work.

Edit: if you're using Google's deb, you have to run google-chrome with the --enable-plugins switch. The deb adds their repo to sources.list.d, but I have no idea when they'll enable plugins by default in their repo. I'd ride the chromium-daily channel, since lots of shit is broken anyway.

[1]: http://groups.google.com/group/chromium-dev/browse_thread/th...

For those running Ubuntu AMD64, you can put both 32 and 64-bit versions of libflashplayer.so in ~/.mozilla/plugins (call them libflashplayer32.so and libflashplayer64.so if you like), and 32-bit Firefox will load the 32-bit plugin, and Chromium 64-bit will load the 64-bit plugin. You can get the 64-bit Flash plugin here:

http://labs.adobe.com/downloads/flashplayer10.html

And if anyone's wondering why I'm not running 64-bit Firefox 3.5, it's because the Ubuntu (and possibly Debian, I've no idea) packagers still have it branded 'Shiretoko', which throws off every site searching for 'Firefox' in your UA. Hopefully by Karmic's release they'll have this sorted out.

Also, why does Mozilla not provide 64-bit builds?

On the other hand, Chromium under GNU/Linux distributions is nowhere near there, probably due to the excess embedded code copies.

Reply on news.ycombinator.com