On 2/23/2012 10:27 AM, C wrote:
On Thu, Feb 23, 2012 at 16:22, Steven Hess<flamebait@gmail.com> wrote:
What I plan on doing is what I've been doing which is using Google Chrome. ADOBE Inc can do as it wishes. I get stable Chrome releases with regularity. I refuse to be overly paranoid abut Google.
I find Chromium to have some issues... I've been using it as a primary browser since I installed openSUSE 12.1... webpages sometimes end up all black with a blue border... ie unusable and unreadable. Sometimes reloading the page several times will get it to render. This happens mainly with YouTube pages, but not always... sometimes other pages. I had one page a few days ago that would pulse (for lack of a better word) from fully rendered to the black with blue border thing.
It's weird... I still am using Chromium... but... it's less than usable some days. :-P No idea if "Chrome" would be better than Chromium here...
C.
You need multiple browsers always. 1) Any one becomes too dominant and it warps the standard around it's particular idiosyncrasies, and then everything else has to become "bug-compatible" or else effectively break through no fault of their own, and things that can't possibly change like everything that's already been written and embedded simply break, also through no fault of their own. 2) And of course nothing is perfect so no matter what you need ready alternatives for those times when the wunderkind fails. I happen to use chrome wherever possible by default these days. Well for some reason I have yet to track down, on my little Vaio P (that's why I haven't tracked the problem down, this device is hardly really useful except as a toy to play with) running ubuntu and lxde and the accursed gma500 graphics chip, both chrome and chromium crash my entire X session, not just the browser, not just lxde, but the X server itself (if it were just lxde crashing, I'd be dropped back to the xdm-alike not all the way back to a shell.) Restart X and repeat the crash 2 or 3 times and the entire box locks up and I have to power-cycle it. Firefox doesn't. It's been the same way through at least 3 ubuntu version upgrades, which means who knows how many chrome/chromium updates, several kernels, several versions of emgd driver. It's probably actually just something bad in the users profile, cache, settings, etc, ie fixable, but it doesn't matter what it is. It still shows that chrome behaves different than firefox and there is a demonstrable situation where chrome causes, directly or indirectly, an unusually catastrophic crash, and firefox doesn't. Simple answers aren't. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org