More to the point of this post however is that Mr. Stavracas gave a shout out to Endless for supporting his work on a fix for this bug. It was nice to read of Endless’ involvement and support in fixing this bug that had a wide spread impact on the whole Linux community.
In fact, both Georges (@feaneron) and Philip Chimento (@ptomato), who has also been working on these fixes, are employed by Endless. We employ a number of GNOME contributors, both developers and non-developers alike. We are deeply tied to them as our upstream, and make sure that we are helping them as much as they are helping us
This kind of problem is specially crucial for us at Endless, since it impacts our users more than regular, enterprise-level users. And, obviously, we care about out users
Notice, though, that, while a lot has been done, there is still a long road ahead to properly control the many misbehaviors and memory leaks that the Linux stack has. We’ll keep transparently communicating these improvements to the community.
Thanks again for reaching out, appreciation is always welcomed
I came across Philip Chimento’s (@ptomato) blog post this morning https://ptomato.wordpress.com/ with more coverage of Gnome Shell resource usage. He again mentions Endless.
I have something of a soft spot for new and interesting UIs (remember Meego, Remix?). I think it is validating for a new OS to be keeping a focus on work that has spawned them. And personally speaking coming across Endless’s commitments to the broader community makes me more confident in using Endless.
