Comment by charcircuit
21 hours ago
>GrapheneOS is not solving the actual interesting problem
Consumers don't care how interesting the developer's problems are. They want their own problems to be solved and GrapheneOS does a better job of that.
>running on an entirely mainline kernel
Google already did that work years ago. Android will work on a mainline kernel. Just like with x86 the mainline kernel needs to support the hardware e you want to use though.
> and GrapheneOS does a better job of that
While Google is allowing that.
> Just like with x86 the mainline kernel needs to support the hardware e you want to use though
Librem 5 runs on all free drivers. This is why it will never be tied to an old kernel. This doesn't work with GrapheneOS.
>While Google is allowing that.
And while Linus allows Linux to be open source. A benefit of open source is that you can fork it if upstream decides to stop development or go closed source.
>This doesn't work with GrapheneOS.
GrapheneOS can use free drivers too. It literally is using Linux.
> And while Linus allows Linux to be open source.
Linus can't close the kernel. He would need to ask all contributors for a signed agreement for that. This is the benefit of GPL.
See also: https://news.ycombinator.com/item?id=46177148
> GrapheneOS can use free drivers too. It literally is using Linux.
Except there is no device with free drivers that it supports. They just refuse to support Librem or Pinephone without a good reason. (I strongly disagree with their "security" arguments.)
> A benefit of open source is that you can fork it if upstream decides to stop development or go closed source
Android is already semi-closed (see this submission). Are GrapheneOS developers forking it? (No)