4 ms·

If you want this and still want the polish of Fedora + Gnome, try SilverBlue - https://silverblue.fedoraproject.org/ https://silverblue.fedoraproject.org/ Buil

If you want this and still want the polish of Fedora + Gnome, try SilverBlue - https://silverblue.fedoraproject.org/ https://silverblue.fedoraproject.org/ Built on Project Atomic (https://www.projectatomic.io/ https://www.projectatomic.io/) and OSTree (https://fedoraproject.org/wiki/Changes/WorkstationOstree https://fedoraproject.org/wiki/Changes/WorkstationOstree) You can achieve the exact same thing. e.g. here - https://discussion.fedoraproject.org/t/minimal-or-custom-silverblue-ostree-images/1574 https://discussion.fedoraproject.org/t/minimal-or-custom-sil...

michaelmrose 7y ago
To put it kindly Fedora has never been a polished experience and gnome still hasn't fixed its memory leak that they spent a, decade pretending not to notice.
- geolgau 7y ago
  I've used Fedora (albeit not with Gnome) for more than 5 years at my job and didn't have major issues with it. If you're the kind of people that think Fedora = Gnome, then that's not true. You can have Fedora and run KDE, XFCE and whatever else you want. But I agree, Gnome sucks.
  - michaelmrose 7y ago
    Fedora by being a testbed for RHEL will always have the goal of testing things before they are ready and will NEVER have the goal of providing an optimal experience.
- adipginting 7y ago
  Them memory leak on Gnome shell is fixed on version 3.28.4 for me. It was memory-leak on Ubuntu 14.04 but they fixed in 14.04.2. The "a decade" claim needs some evidence.
  - michaelmrose 7y ago
    The memory leak is the result of a poorly designed interface between compiled code and javascript. The result being that memory wasn't truly leaked in the traditional fashion but rather was consumed rapidly and freed on no sane timescale. This mismatch between compiled code and javascript existed from inception to now. The fix if I understand it correctly is to really aggressively free memory in a fashion that appears grossly inefficient but in practice performs acceptably. The release of gnome 3 was in spring of 2011 the "fix" was released in spring of 2018. It would be more accurate to say that it was terribly broken only for the first 7 years of its existence. Because their "fix" is a hacky workaround for the fact that the only true fix is to throw everything away and start over the bug is actually back in 3.34 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1740 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1740 This brings us to an 8th year of shipping a broken product heading for year 9. That this was a bug that sprung into being in ubuntu 14.04 and was fixed in a point release is totally incorrect.

michaelmrose 7y ago

To put it kindly Fedora has never been a polished experience and gnome still hasn't fixed its memory leak that they spent a, decade pretending not to notice.

geolgau 7y ago
I've used Fedora (albeit not with Gnome) for more than 5 years at my job and didn't have major issues with it. If you're the kind of people that think Fedora = Gnome, then that's not true. You can have Fedora and run KDE, XFCE and whatever else you want. But I agree, Gnome sucks.
- michaelmrose 7y ago
  Fedora by being a testbed for RHEL will always have the goal of testing things before they are ready and will NEVER have the goal of providing an optimal experience.
adipginting 7y ago
Them memory leak on Gnome shell is fixed on version 3.28.4 for me. It was memory-leak on Ubuntu 14.04 but they fixed in 14.04.2. The "a decade" claim needs some evidence.
- michaelmrose 7y ago
  The memory leak is the result of a poorly designed interface between compiled code and javascript. The result being that memory wasn't truly leaked in the traditional fashion but rather was consumed rapidly and freed on no sane timescale. This mismatch between compiled code and javascript existed from inception to now. The fix if I understand it correctly is to really aggressively free memory in a fashion that appears grossly inefficient but in practice performs acceptably. The release of gnome 3 was in spring of 2011 the "fix" was released in spring of 2018. It would be more accurate to say that it was terribly broken only for the first 7 years of its existence. Because their "fix" is a hacky workaround for the fact that the only true fix is to throw everything away and start over the bug is actually back in 3.34 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1740 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1740 This brings us to an 8th year of shipping a broken product heading for year 9. That this was a bug that sprung into being in ubuntu 14.04 and was fixed in a point release is totally incorrect.