5 ms·
They already made their own thing for Chrome OS rather than use GTK/Gnome or Qt/KDE there. I find it sad that they felt the need to make their own UI engine vs
by paulyg 13y ago
They already made their own thing for Chrome OS rather than use GTK/Gnome or Qt/KDE there.
I find it sad that they felt the need to make their own UI engine vs being able to contribute the changes they feel they need to an existing project. I'm sure Google engineers will tell you that they need to move faster than they could working within the community of GTK or Qt. Plus they don't want Chrome OS to suck because they can't get features merged by the community. They are valid points. The resulting fragmentation just sucks.
I assume Aura is open source. Given GTK's dropping adoption rate and a lot of people unhappy with the recent direction (design or lack of listening to current user base) of Gnome how long until someone writes a general purpose (not specific to Chrome OS) window manager/desktop environment on top of it?
- Touche 13y agoI don't see that ever happening. Google does a lot of reinventing the wheel with their projects and most of it is not built in a way that is easily useable in downstream projects, and they probably won't accept patches anyways. Chromium OS, for example, could have been forked and used in a lot of cool ways but that hasn't happened yet and I doubt it will.
- threedaymonk 13y ago> Chromium OS, for example, could have been forked and used in a lot of cool ways but that hasn't happened yet and I doubt it will. Well, there's CoreOS, though the end result is rather different.