1: https://redlib.catsarch.com/r/GooglePixel/comments/1wr1767/c...
The lags are actually quite unpleasant and noticable, i wonder how it wasn't caught before the release.
Am I surprised that a bug happened in Pixel? Sure. Is there a cause to call for better processes? Yes. But saying "well well well, I fixed the bug" just comes across very amateur.
The point of the post is not that grapheneos made the fix, it's that they had to.
This is such a rarity to see in today's world. I'm glad GrapheneOS is getting the support it needs. I wish that happened more often.
I'm curious if there's any back up plan to an operating system used by billions. One would think, and hope, the EU would have an alternative ready to go at a moment's notice. Android is literally too big to fail, but I doubt the EU would be ready even though you could consider the failing of Android a national security emergency.
I would like to know more about what's going on at Google that are causing these issues.
AOSP and the Android SDK are open source. GrapheneOS is exactly an alternative to Google Android. Sure, Google could shut down the Play Store (but alternative stores exist), or destroy the Play Services (but even then, there is microG).
I am happy that Google is still contributing to Android because they have a ton of money and many brilliant engineers, even though as a company it seems like it's somehow trying to burn it to the ground. But I am optimistic: it would be possible to build on top of the open source parts of Android if needed.
> So it's concerning to see this move from Google, which is also the device vendor for all currently supported GrapheneOS devices.
It is, and the solution to that is the partnership with Motorola.
GOS can just talk about the upside, their solution to this problem. That's great work. But they often choose to denigrate others, which is destructive, damages relationships (the most essential assets - especially when you have no money to offer!), and is myopic: GOS's sh-t stinks too; they f- things up too. Forgive us our trespasses as we forgive those who tresspass against us.
It seems especially dangerous being entirely dependant on Google's goodwill; Google has zero need for GOS. I'd think Motorola, who now has money and reputation depending on GOS's success, would tell GOS to zip it. If I were in that industry and looking to partner, I might love GOS's technology but their behavior would be hard to overcome. For example, I love OpenBSD, but who partners with them? And OpenBSD isn't dependant on someone else.
Just zip it, be professional, focus on what you are doing and not on others. Great job on this fix!
It used to be like that (and to be fair, all the similar communities were contributing to the drama, not just GOS), I agree, but I genuinely feel like it has become a lot more professional lately. Like I haven't seen drama in... at least 6 months?
Now I almost exclusively see them explain their technical decisions, which is very interesting.
How do you propose they "focus on what [they're] doing and not on others" when their entire project is dependent on other's (Google's) work that directly impacts their own users? There's nothing about this blog post that is unprofessional. GrapheneOS released a patch for a rather severe performance bug, which is outside the scope of their normal work, so they provided context into why they made the decision to do so.
The article uses phrases like "completely broken", "awful", and "<delay> wouldn't be a surprise". Which might be true but it's not helping.
There's a certain humility in how Igalia conducts business, and they contribute sooo much to the web ecosystem.