4 ms·
> Until now, Nexedi has been maintaining a derivative of ChromiumOS with some extra features: NayuOS. However, the gap between ChromiumOS and its proprietary co
by mlinksva 7y ago
> Until now, Nexedi has been maintaining a derivative of ChromiumOS with some extra features: NayuOS. However, the gap between ChromiumOS and its proprietary counterpart ChromeOS has increased so much that we see no possibility to maintain a usable NayuOS in the long terme.
In what ways has the gap between ChromiumOS and ChromeOS increased? Is that true of Chromium and Chrome as well?
> Nexedi has thus decided to support the /e/ foundation and its sister corporation, with the hope that /e/ would some day become a usable OS for desktop or laptop.
Good for them, I think/hope!
- zamadatix 7y agoI haven't worked with ChromeOS/ChromiumOS all that much but Chrome/Chromium aren't very different at all.
- zifnab06 7y agoI have one qualm with /e/: they use LineageOS as their base, add a few apps, and avoid mentioning this to anyone. Most of their repos aren’t special, they’re a 1:1 copy of upstream. I realize the license allows this but attribution would still be appreciated.
- smetsjp 7y agoWhat you do not get in ChromiumOS (last time I checked): - support for flash movies - support of certain video codecs - support of sound hardware of many recent Chromebook models - support of CJK input (at least in Guest Mode) - support of Android apps - support of Linux virtual machine subsystem - support of certain Google APIs (but that is OK for me) Lack of stable support of CJK input in guest mode (and the difficulty to find anyone capable of solving this problem or supporting us) was the biggest issue for me. Some years ago, the difference was: - support for flash movies - support of certain video codecs - support of certain Google APIs (but that is OK for me) which was fine to me. Note: I wrote the article on /e/ for Desktop
- smetsjp 7y agoWhat you do not get in ChromiumOS (last time I checked): - support for flash movies - support of certain video codecs - support of sound hardware of many recent Chromebook models - support of CJK input (at least in Guest Mode) - support of Android apps - support of Linux virtual machine subsystem - support of certain Google APIs (but that is OK for me) Lack of stable support of CJK input in guest mode (and the difficulty to find anyone capable of solving this problem or supporting us) was the biggest issue for me. Some years ago, the difference was: - support for flash movies - support of certain video codecs - support of certain Google APIs (but that is OK for me) which was fine to me. Note: I wrote the article on /e/ for Desktop
- jdnenej 7y agoFlash is long dead and gone. Chrome OS probably also doesnt support floppy disk's.