I'm curious why you care about whether or not they spent time and effort to write those components themselves. Isn't that their choice as the authors? How does it materially affect you or the product experience? From my vantage point, I love the idea of having even more options as it will create competition, making all sides better for it. Having a singular dominant player in any space (whether it's a browser, kernel, or library) is something we should try to avoid whenever possible.
They don't need to do that to sell their hardware so why would they do that? On the other hand, they have strong incentives to not give you that level of access and information. The only way this will change is by having some disruption by way of a competitor who sells hardware with that feature as being a major reason why it takes off.
Security at its core comes down to trusting the supply chain that provides the software that runs on your hardware. There are many alternative secure supply chain models, but ultimately users often are incapable of making great choices on what is trustworthy. It does generally make sense that the OS vendor needs to play a key part in helping ensure trusted parties are involved in the supply chain.
Comparing phones to PCs isn't a great comparison because PCs don't have a great track record and the amount of personal data and ease of installing lots of apps is quite different. Of course the current arrangement is far from perfect, but acknowledging the problems it's trying to solve is an important step towards trying to find a solution that is better.
Having been on the flip side of this divide in the past, there really are a lot of potential safety and reliability problems when using random third party versions of components. While I'm sure there are strong financial incentives to constrain supply, there are also some other strong reasons as well.
Also it's very expensive to actually make an ecosystem compared to a close one. The best way to incentivize manufacturers to do it is by creating a competing product that is open and having that differentiating feature drive sales away. That's generally the approach that works best.
I saw this happen a bit earlier this year, but most everyone I work with has learned that it was foolish. The feedback that they are doing something wrong needs to be explicit and strong. We're all going through a learning curve and establishing cultural norms is important at this time.
Most of it comes down to avoiding shared data. Unfortunately it requires forethought to do that well. There are also many cases where you do want to share data for optimal performance as other options are ultimately too heavyweight.
Also worth noting that an event loop by itself doesn't give you serialization by itself, it can just allow you to gain concurrency without parallelism. You still need some form of serialization by way of something like actors (or async locks).
My suggestion is to not try to idolize individuals. Products should be judged independent of the individuals involved in creating them, especially when many individuals participate in their creation.
People are all flawed. You can find faults in everyone. Overlooking these flaws is okay to a large number of folks as the product itself is amazing. The fact is that you're likely ignorant to the large number of products and services you use produced by folks with similar flaws.
This feels like the sort of thing that needs to be legislated. Banning accounts after breaking ToS is a pretty common behavior across many companies. The fact a Google account ends up being used for multiple products makes it more interesting but the overall problem here is not unique to them.
No, shared peripherals need to go through a central arbiter for access. In the case of things like storage the AP's OS, eg android, provides that roll. This is also true for the OS that runs under the trustzone. Be careful about spreading rumors without validating them.
The perception that they are able to run rings around Google is not necessarily an accurate one. There are tradeoffs in any engineering situation and GrapheneOS devs make different ones based on different requirements. Google is one of the reasons MTE even exists. I don't think GrapheneOS devs would be capable of helping push forward that technology in the same capacity.
I've written systems level code (drivers and os code) for years and outside of ffi, I've managed to go on year long stretches without touching unsafe. It's really not a commonly needed tool in a well architected code base with good libraries to encapsulate common reasons it might otherwise be necessary. And we don't really consider using unsafe taboo, it's just not necessary.
That's a cultural thing. Push back on it and don't make it acceptable behavior. I would argue most people generally are terrible at code review and do this same behavior with their peers as well, but at least their peers are capable of owning some level of responsibility, whereas the LLM is not.
In some cases it's just because the userbase using the web on their phone instead of the app is incredibly small and it's not worth funding feature parity. It can be difficult to distinguish this case from more hostile takes like reddit and Twitter.
Most YouTubers still have sponsor sections on their videos so you probably do see some ads. Also why not pay for YouTube premium to remove the ads while still supporting the creators?
Continuous load is not the use case the beefy cores on phones are designed for. They exist for bursty loads related to user interactions. Humans are fairly slow, but each touch can generate a substantial workload. Being able to handle that workload quickly and then sitting idle is what these cores do. Continuous load runs on the smallest cpus possible or ideally offloaded entirely from the CPU to others subsystems. The goal here is to minimize power usage while maintaining good user experience.
It's one thing for a maintainer to use AI, and another to review AI code sent your way. The latter has been proven to be unsustainable, low value, and ultimately a challenge for open source. Everyone acknowledges this problem exists and some corrective action is required to mitigate it.
risc-v is basically borrowing the ARM SystemReady stuff. This includes the expectations for ACPI and UEFI on servers. The RISE organization has been trying to drive these standards iiuc.
Considering how consolidated the hyperscalar market is and their natural inclination to reduce hardware SKUs, I'm not entirely sure they would make it viable for multiple vendors to produce chips they could actually use. There is no reason to believe it'll work out differently from the ARM server market.
Who is funding this security audit? Are folks supposed to volunteer their free time? It's a difficult coordination problem. The best folks have come up is to delay adopting new releases by a few days and hope your dependency is popular enough that a security firm audits it for you in that timespan. If you have enough money I suppose you can start employing llms to audit things for yourself.
The longer you starve the more delicious the food tastes. Programming language advances were ignored by a significant number of folks for decades. The sudden relief of getting something like rust can leave a strong impact.
People also like community and rust has a decent one. It's not wrong for folks to want to feel part of a community they have shared interests or values with.
What enterprises pay for is all that matters. They pay insane amounts for a lot of things I would never do personally, but I'm not the target demographic in those cases.