Owen Williams, writing for Motherboard:
One of the biggest problems today is that despite Chromium’s
popularity, it’s really not very good on the resource front: it
drains battery, hogs system resources and generally doesn’t play
nice. This, largely, has been because Google and Chromium don’t
own their own operating system (outside of ChromeOS), and don’t
get exclusive access to low-level system APIs that Safari and Edge
There’s a lot I disagree with in this piece, but this bit takes the cake. “Really not very good on the resource front” ought to be nominated for understatement of the year. Safari isn’t more efficient because it has “exclusive access” to system APIs. It’s more efficient because the WebKit/Safari team places a higher priority on efficiency than Chrome’s team does. It’s that simple.
This difference in priorities is why Google forked Chrome’s rendering engine from WebKit in 2013. Which, in turn, makes me wonder what the endgame will look like with Microsoft adopting Chrome. Is Microsoft really going to stick with Chrome, under Google’s ultimate control, or will they fork it, the way Google forked WebKit?
Update: Owen Williams just admits he made this shit up about using private APIs.
★ Monday, 10 December 2018