Even if you have no issue with Google, this is still a good idea to encourage competition. Honestly, Chrome is not as good as it used to be anyway. For me, Google Maps and Waze are the hardest things to kick. And YouTube...
Apple Maps is now quite usable if you're on iOS...although it's no Waze.
No to Chrome
141–150 of 319 posts
Re: No to Chrome
#142Earlier quoted context omitted.
It's better to provide facts and references rather than just making opposing statements.
The burden of proof is for the original statement ("it's literally the same engine"), not the counter.
Re: No to Chrome
#143Earlier quoted context omitted.
Firefox uses the Gecko engine, while Chrome uses Blink. The engines don't even have a shared ancestor.
“Originally” if I recall correctly, Chrome was a fork of firefox right? That is a long time ago though!
Edit: It was widely speculated that Apple would use gecko for Safari and a shock when they announced they would use the relatively little known KHTML engine. The decision was based on KHTML having much cleaner code. I haven't looked at the Mozilla code in many years, but it was pretty gnarly back then. Lots of old cruft from the Netscape days. In comparison, KHTML was beautiful.
Re: No to Chrome
#144Earlier quoted context omitted.
I was using Safari up until they have yanked support for extensions. The web is unusable, outright hostile place without a proper script blocker. I can tolerate a lot of things, but browsing the web without uBlockOrigin isn't one of them.
I'm loving pihole https://pi-hole.net/
Re: No to Chrome
#145Earlier quoted context omitted.
They scrape top results and show it directly in a box (think wikipedia, imdb, lyric engines etc.) thus discouraging users from actually clicking the link. Personally, I think it’s nice to have the content instantly available and not having to go to a website for it but I can see how for content producers this means wrapping their websites and making money out of their content.
Wasn't that something their search copied from ddg?
Also, DDG's "Instant Answers are open source and are maintained on GitHub, where anyone can build or work on them". https://en.wikipedia.org/wiki/DuckDuckGo
It's not the same sort of massive web-scraping click-stealing operation as Google's OneBox.
Re: No to Chrome
#146Is it better to push people to firefox and safari or include Opera and Edge as well so we don't get another defacto standard?
Re: No to Chrome
#147Re: No to Chrome
#148Earlier quoted context omitted.
OpenStreetMap had solid data, but my periodic attempts at finding a good app haven't been successful.
https://maps.me/ is a pretty mainstream option.
Re: No to Chrome
#149Interesting, I just moved back to Firefox after many years of using Chrome. I have to admit, it has gotten a lot faster recently, Firefox sync is working very well, and the Firefox Android app is a pleasure to use (being able to install uBlock origin is a huge plus). Anything else I missed on Chrome was easily solved by an addon, or a small tweak on userChrome.css (customizing the browser interface by overriding its…
Has firefox solved its long standing issue with the rendering of radio buttons?
Re: No to Chrome
#150Chrome/ium is a wonderful web development environment. Can't see myself moving away from it any time soon.
I used to think the same, but now do all web dev in Firefox. For my purposes it has parity with chrome, and works just as well. Also means if it works in Firefox it will most likely work in chrome. The opposite was not always true.
Can’t relate at all. In my limited frontend experience, I’ve run into a lot of rendering deferences between WebKit and Blink, and even more between Gecko and Blink. Sometimes the differences are subtle yet break pixel perfection; sometimes the whole layout is broken.