You could probably make a small Arch install, add LibreOffice and something either like the GNOME browser or Firefox. What people using ChromeOS want is something light (for cheaping out on hardware to schools), and basically just a way to access a browser. Plus, something something permissions. ChromeOS is marketed towards enterprise, like education. Just need the bare minimum to get on the 'net, and no more.
Why the hell would you use arch for browser centric use? Literally any stable distro would work perfectly fine, and doesn’t risk failing to boot because of an update…
I think an immutable distro like Bazzite’s cousins Aurora (KDE) and Bluefin (GNOME) would be far more appropriate. Combined with automatic rollback (if the system fails to boot, rollback to previous version) and it’d be practically bulletproof in education.
In reality, what Chromebooks provide is a reinvention of the good old mainframe and terminal principle. In theory (like my recent - half joking - 9front comment) this is something that would be really easy to set up with nearly all Linux systems and especially immutable ones.
My take would be:
Put an sign up / sign in form as a “first boot” message in a distribution of your choice where you can specify (or have pre-filled by an organisation) a central server (could be something fancy like Nextcloud or something simple rsync based) where your whole profile folder gets synced to. After that: If anything goes kaputt just roll back the sync. Or “powerwasch” (to keep the ChromeOS terminology) the system to a clean state and re-sync your home folder.
In theory something that could all be implemented with a little scripting in an afternoon.
You could probably make a small Arch install, add LibreOffice and something either like the GNOME browser or Firefox. What people using ChromeOS want is something light (for cheaping out on hardware to schools), and basically just a way to access a browser. Plus, something something permissions. ChromeOS is marketed towards enterprise, like education. Just need the bare minimum to get on the 'net, and no more.
Why the hell would you use arch for browser centric use? Literally any stable distro would work perfectly fine, and doesn’t risk failing to boot because of an update…
Because arch btw 🙄
I think an immutable distro like Bazzite’s cousins Aurora (KDE) and Bluefin (GNOME) would be far more appropriate. Combined with automatic rollback (if the system fails to boot, rollback to previous version) and it’d be practically bulletproof in education.
In reality, what Chromebooks provide is a reinvention of the good old mainframe and terminal principle. In theory (like my recent - half joking - 9front comment) this is something that would be really easy to set up with nearly all Linux systems and especially immutable ones.
My take would be:
Put an sign up / sign in form as a “first boot” message in a distribution of your choice where you can specify (or have pre-filled by an organisation) a central server (could be something fancy like Nextcloud or something simple rsync based) where your whole profile folder gets synced to. After that: If anything goes kaputt just roll back the sync. Or “powerwasch” (to keep the ChromeOS terminology) the system to a clean state and re-sync your home folder.
In theory something that could all be implemented with a little scripting in an afternoon.