4 ms·
By now most of the early adopters of Firefox have moved over to Chrome I'm experiencing the opposite. Google's handling of what used to be a good browser has p
by trezor 15y ago
By now most of the early adopters of Firefox have moved over to Chrome
I'm experiencing the opposite. Google's handling of what used to be a good browser has provoked me to the point that I do not feel comfortable using Chrome. I've moved back to Firefox because it's a browser which I can control, not a browser which controls me.
Chrome's primitive and failed extension-model (still) also makes Firefox look better when compared head to head.
Chrome used to be a browser for techies, but is now merely a good mom & dad browser. Because Google explicitly drove development in that direction. It will probably gain market-share as consequence of that (and because Google is advertising it fucking everywhere). However, power-users will probably leave Chrome now that Google has used them to promote it and no longer sees any need to appeal to them.
In fact, Google seems outright hostile against any power-user needs at every single point, bar the web-development module. Everywhere else Google is dumbing things down at the expense of technical detail. As a power-user I find this extremely unsexy.
- BvS 15y agoCould you give some examples of what Google has changed to make Chrome a worse browser?
- trezor 15y agoThere has been several, but I've been back on the FF-wagon for a while now and it's hard to remember them all. Examples of things which did seriously annoy me: URL protocol-obfuscating. Besides being an aesthetic nitpick (lack of consistency) it allows creating confusing and irregular behaviour with copy & paste. There was a massive backlash of power-users wanting this toggleable to no avail. Google's response was basically "we make defaults, not options". Google's anti-Flash Jihad with added causalities. I never had any issues what so ever with Flash in Chrome. Not once did Flash crash my browser. Never. But immediately when Google decided Flash was a stability risk and intervened to isolate the browser from Flash, instantly the result was that having Flash installed or active would always crash Chrome no matter what. Basically Google forced me to uninstall or disable Flash entirely if I wanted to use Chrome. Just because they said so. They made the decision and didn't make their anti-Flash jihad an option for me to enable or disable. You would think Chrome suddenly crashing on its own for no reason would be considered a high-profile bug, but this was not fixed at all in any subsequent updates. After 3 updates without any fix Google had lost me entirely. I'm not even using Google Chrome for development purposes or verification at this point. The product is so overly Google-driven and Google-decided that it's not of any interest to me what so ever as a end-user who wants more than defaults, be they set by MS or Google.
- ezyang 15y agoFWIW, dropping http landed in Firefox trunk a few weeks ago, so you can expect it to show up fairly soon. Though, it'll probably be toggleable in Firefox :-)