What would be alternative to Chrome

levmc

macrumors regular
Original poster
Jan 18, 2019
185
5
It seems Chrome is a bit slow.
I'm thinking of either using Brave or Vivaldi as my primary browser.
Which one would be better?
 

Stephen.R

macrumors 68020
Nov 2, 2018
2,057
2,130
Thailand
Both those browsers are using the guts of Chrome anyway.

This is ridiculously ironic in the case of Vivaldi, as it was started by one of the founders of Opera, in protest to Opera's dropping of it's own Presto rendering engine, in favour of... the one in Chrome.
 
  • Like
Reactions: Fuchal

sracer

macrumors G3
Apr 9, 2010
8,522
9,056
Prescott Valley, AZ
It seems Chrome is a bit slow.
I'm thinking of either using Brave or Vivaldi as my primary browser.
Which one would be better?
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.
 
  • Like
Reactions: ignatius345

bogdanw

macrumors 6502a
Mar 10, 2009
691
371
Last edited:

960design

macrumors 68030
Apr 17, 2012
2,922
892
Destin, FL
I use Safari, but there are alternatives for everybody
Same engine as Chrome, might be faster:
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.
 

bogdanw

macrumors 6502a
Mar 10, 2009
691
371
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.
bibliography :)
https://en.wikipedia.org/wiki/WebKit#Forking_by_Google
https://en.wikipedia.org/wiki/Blink_(browser_engine)
https://en.wikipedia.org/wiki/List_of_web_browsers
 
Last edited:

960design

macrumors 68030
Apr 17, 2012
2,922
892
Destin, FL
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.
 

Stephen.R

macrumors 68020
Nov 2, 2018
2,057
2,130
Thailand
While Apple did create the WebKit engine
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.
 

Wowfunhappy

macrumors member
Mar 12, 2019
85
79
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.
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.
 

960design

macrumors 68030
Apr 17, 2012
2,922
892
Destin, FL
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.
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.
- - Post merged: - -

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.
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:

Similar threads

  • b0redom
3
Replies
3
Views
986
Replies
0
Views
262
  • Tymmz
3
Replies
3
Views
595
  • Long David
2
Replies
2
Views
804
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.