[yjftsjthsd-h]

I don't understand what any of your comment has to do with this thread, which is about security models and application sources.

That said,

> You can have a pinephone, and it will work fine for like 2 hours, warming like hell, and having you wait for minutes for an app to open. That’s where the linux userspace is.

No, that's where the pinephone hardware is. I mean, also it sounds like maybe you have a defective unit because mine doesn't do what you're describing, but this is like judging Android by the cheapest phone I can buy, which is also agonizingly slow. If you don't use a device built out of really old+cheap parts, ex. postmarketos is perfectly fine.

[kaba0]

> but this is like judging Android by the cheapest phone I can buy, which is also agonizingly slow

Nope, even running android on the same pinephone hardware results in a smooth system - it’s almost like google has been spending dollar billions on fixing and developing stuff that won’t magically appear in a userspace stuck in unix times. The kernel did get some upstreaming, that’s why linux laptops are remotely portable.

But for a mobile device you need a used space that understand the resource-constrained environment and are good citizens. This makes a huge difference in an age where racing-to-suspend is the way to conserve battery.

[seba_dos1]

Just because Android can bypass PinePhone's underpowered GPU when doing some of the animations doesn't mean the whole system gets significantly smoother. There's nothing preventing phoc or KWin from doing the same, aside of its relatively low priority on development roadmaps as other devices don't suffer so much from it.