wizard10000 wrote:I've had three showstoppers in the past six months and that's more than any other package I have installed.
wizard10000 wrote:All three of my machines have chromium installed but on the 64-bit machines chromium's config and cache directories are just symlinks to Chrome's config and cache.
kcbagr wrote:Google Chrome has been more reliable for you?
kcbagr wrote:The symlinks would require that Google Chrome be installed though, right? What is done on boxes where only Chromium is installed?
kcbagr wrote:Just stop it! This thread is not a statement on whether one browser is better than another. It is intended for those people who use Chrome or Chromium. Others need not reply.
cpoakes wrote:kcbagr wrote:Just stop it! This thread is not a statement on whether one browser is better than another. It is intended for those people who use Chrome or Chromium. Others need not reply.
Save for a single post, no one has mentioned a non-Chrome derived browser - so this is certainly not a discussion about which non-Chrome browser might be better.
This is a Debian forum where discussing Debian issues including the DFSG and release stability is entirely relevant. My prior post enumerates reasons to avoid both browsers based on the DFSG (avoid DSM), and the guideline "Don't break Debian" (chromium EOL in wheezy). These are relevant factors in choosing chrome or chromium, as well as none of the above. If you think this is not relevant, your survey belongs in "Offtopic" or on some other forum.
cpoakes wrote:C. None of the above
I don't use a browser locked into DRM.
And not a fan of chromium as the devs don't take Debian Stable seriously. Wheezy chromium hit end-of-life/no security support in January 2015 months before jessie went stable. You either had to move from stable (wheezy) to testing (jessie) before it was ready; download and use Chrome; or move to another browser. Those of us who 1) used chromium, 2) only use stable, and 3) use the year overlap between stable and oldstable to transition systems were hung out to dry.
kcbagr wrote:...DRM aversion with Chrome and security update concerns with Chromium.