3 ms·

Separate but relevant news[1] is that Google seems to be separating "ChromeOS" from the Linux portion and using Wayland rather than the ChromeOS-specific "Freon

Separate but relevant news[1] is that Google seems to be separating "ChromeOS" from the Linux portion and using Wayland rather than the ChromeOS-specific "Freon" graphics stack. [1] https://arstechnica.com/gadgets/2023/08/google-is-finally-separating-chrome-from-chromeos-for-easier-updates/ https://arstechnica.com/gadgets/2023/08/google-is-finally-se...

iforgotpassword 3y ago
Tried it on my Samsung Chromebook that ran out of support last month. The system is stuck on 114 but the browser is now 115. But, the device not being the fastest anymore, has gotten notably laggy with this, because I guess now I really have two different versions of chrome running simultaneously.
- quag 3y ago
  I think I have the same chromebook model as you (Samsung Chromebook Pro). Do you have any tips or advice for trying it or anything else that will let me keep using the device?
  - iforgotpassword 3y ago
    I guess lacros is actually the easiest option. It's just a toggle in about:flags, but as said it gets notably laggy and sluggish when browsing. The upside is that it reduces the attack surface by allowing you to have an up to date browser for the foreseeable future, compared to just staying on 114 for as long as it still gives an acceptable browsing experience. I still want to try and install Linux on it for fun some time, but I don't expect that to result in a much better browsing experience either.
resoluteteeth 3y ago
I'm not sure this will affect that much for users except that EOL devices will still get browser updates (which I think was the main goal) I guess it will probably also slightly simplify development of both chromeos (because it won't have a bespoke graphics stack) and chrome (because there will be one less version) for google, too.
ankurdhama 3y ago
I don't think they are removing Freon. It seems the shell/window manager will still be based on Freon and Chrome will be linux version of chrome that will use wayland (as chromeos already have a wayland implementation called exo which is used by ARCVM and Crostini)

iforgotpassword 3y ago

Tried it on my Samsung Chromebook that ran out of support last month. The system is stuck on 114 but the browser is now 115. But, the device not being the fastest anymore, has gotten notably laggy with this, because I guess now I really have two different versions of chrome running simultaneously.

quag 3y ago
I think I have the same chromebook model as you (Samsung Chromebook Pro). Do you have any tips or advice for trying it or anything else that will let me keep using the device?
- iforgotpassword 3y ago
  I guess lacros is actually the easiest option. It's just a toggle in about:flags, but as said it gets notably laggy and sluggish when browsing. The upside is that it reduces the attack surface by allowing you to have an up to date browser for the foreseeable future, compared to just staying on 114 for as long as it still gives an acceptable browsing experience. I still want to try and install Linux on it for fun some time, but I don't expect that to result in a much better browsing experience either.

resoluteteeth 3y ago

I'm not sure this will affect that much for users except that EOL devices will still get browser updates (which I think was the main goal) I guess it will probably also slightly simplify development of both chromeos (because it won't have a bespoke graphics stack) and chrome (because there will be one less version) for google, too.

ankurdhama 3y ago

I don't think they are removing Freon. It seems the shell/window manager will still be based on Freon and Chrome will be linux version of chrome that will use wayland (as chromeos already have a wayland implementation called exo which is used by ARCVM and Crostini)