Chrome 58 Makes Its Debut

[phoronix]

Phoronix: Chrome 58 Makes Its Debut

Not long after the Firefox 53 release, Google has promoted Chrome 58 to stable...

http://www.phoronix.com/scan.php?page=news_item&px=Chrome-58-Released

[wargames]

Come on Mozilla, Firefox is only at 53 and Chrome is at 58. You need to increase the version number! As everyone knows, when something is higher it means it is better. You are gonna lose lusers.

[danieru]

Come on Mozilla, Firefox is only at 53 and Chrome is at 58. You need to increase the version number! As everyone knows, when something is higher it means it is better. You are gonna lose lusers.

lose lusers LOL

[perpetually high]

Aw man, this new startup animation is very choppy. Was so smooth before in 57. Ok I'm done complaining.

[uid313]

Is it build with GTK 3 yet?

[cl333r]

Is it build with GTK 3 yet?

Hold your horses, maybe you also want it to run natively on Wayland?!

[HyperDrive]

Hold your horses, maybe you also want it to run natively on Wayland?!

Well, yes.

[FishPls]

I wonder if this is the version that uses TurboFan + Ignition instead of Crankshaft. Very excited about that, and the possible memory savings it'll bring once they're comfortable with completely dropping Crankshaft and thus no longer having to keep JS source strings in memory.

[uid313]

Hold your horses, maybe you also want it to run natively on Wayland?!

Yes, absolutely!
But Chrome 57 is built using GTK 2 which means you can not run it natively on Wayland since GTK 2 does not have any Wayland backend.
It is rumored that sometime after Chromium 57 they would enable the GTK 3 backend.
Enabling the GTK 3 backend doesn't necessarily mean that it will work on Wayland since there can still be X11 calls and other libraries which depend on X11, but its a step in the right direction and might mean it works natively on Wayland.

[cl333r]

Yes, absolutely!
But Chrome 57 is built using GTK 2 which means you can not run it natively on Wayland since GTK 2 does not have any Wayland backend.
It is rumored that sometime after Chromium 57 they would enable the GTK 3 backend.
Enabling the GTK 3 backend doesn't necessarily mean that it will work on Wayland since there can still be X11 calls and other libraries which depend on X11, but its a step in the right direction and might mean it works natively on Wayland.

I agree, in just 2-4 years Chrome and maybe Firefox will run natively on Wayland on a Linux distro by default with no work on user's part.