Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What would be alternative to Chrome
- Thread starter levmc
- Start date
- Sort by reaction score
I'm a longtime user of both (and Opera), but I recently stopped using Vivaldi in favor of Brave. Brave feels leaner and faster and has built-in ad blocking that is very effective and efficient.
The most obvious alternative to Chrome (or any other Chrome-based browser) is Safari.
The second obvious alternative to Chrome is Firefox.
The second obvious alternative to Chrome is Firefox.
I use Safari, but there are alternatives for everybody
Same engine as Chrome, might be faster:
Chromium http://www.freesmug.org/chromium
Microsoft Edge https://www.microsoft.com/en-us/edge/business/download
Epic Privacy Browser https://www.epicbrowser.com/index.html
Cliqz https://cliqz.com/en/desktop
Based on Firefox:
Waterfox https://www.waterfox.net
For gaming: Opera GX https://www.opera.com/gx
Same engine as Chrome, might be faster:
Chromium http://www.freesmug.org/chromium
Microsoft Edge https://www.microsoft.com/en-us/edge/business/download
Epic Privacy Browser https://www.epicbrowser.com/index.html
Cliqz https://cliqz.com/en/desktop
Based on Firefox:
Waterfox https://www.waterfox.net
For gaming: Opera GX https://www.opera.com/gx
Last edited:
Fun Facts:
Safari created the WebKit rendering engine, then open sourced it. Chrome used that engine to create its desktop browser and still uses it on its mobile browser. Chrome has always used its own JS engine, which is slightly faster but uses slightly more battery power. Safari opts for the battery savings over the few percentage points on JS execution.
Close but not quite correct. Apple took the already open source KHTML rendering engine, forked it, and continued work on it.
You have an issue with "created", and I see your point, I could have used a better word. While Apple did create the WebKit engine, it evolved from a KHTML fork, just as Chrome evolved from a WebKit component fork.
To complete the history lesson, I'll add that the KHTML team at one point was going to move to WebKit but decided to later continue their work with a hybrid model that supports both KebKit and their own work. In the end KHTML has foundered, with only maintenance updates. WebKit continues to evolve through collaboration of submits by Apple and the KHTML team.
I would agree that they (Apple) created the project around a fork. I know it sounds like I'm being pedantic, but to ignore what they started from is to ignore the contributions (to the KHTML project) that WebKit (and thus Safari, Mail, the App stores, etc) are all built upon.
Chrome uses Blink on both desktop and on Android. On iOS it uses Apple's webkit because Apple does not allow third party browser engines. Every third party iOS browser is basically just Safari with a custom skin.
Just published by Microsoft: "The top 10 reasons to switch to the new Microsoft Edge" https://blogs.windows.com/windowsex...-reasons-to-switch-to-the-new-microsoft-edge/
Not at all pedantic. Pedantic would be pointing out that KHTML was based on KParts.
Everything you've stated is correct, my information should have been better presented.
[automerge]1585594264[/automerge]
Chrome uses Blink on both desktop and on Android.
That is true today, but not for many years.
2008 - 2013ish Chrome used WebKit for rendering
2013 Chrome forked components of WebKit to create Blink
All humbly began as KHML by the amazing KDE team back in 1999.
2002 is when Apple first forked KHTML and open sourced it.
Safari thanks KDE for the hardwork.
Chrome thanks Safari for the hardwork.
KDE thanks Safari for the hardwork.
The point to the OP is that Safari and Chrome both come from the same stock.
Both should work for everything.
Windows took long enough, but has now forked off of the back of Chrome.
Last edited: