Replying to Avatar GrapheneOS

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq76jdt070zywkek27u8vnlhthvvekhkwf53525uc9tj9kujwvcpjsgwzul5 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqhxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3qf3easn nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqrgz3s4 The primary use case is really going to be seamlessly running GrapheneOS virtual machines for improved sandboxing of apps or groups of apps, not other operating systems.

We want to get Windows 11 support working with GPU acceleration support as a demonstration of how powerful the feature can be.

Got it....so mainly for...games? I'm just wondering what the end result will be for normies...or as normie as GrapheneOS users are : P

Reply to this note

Please Login to reply.

Discussion

Solo or small dev teams may not have resources to support both desktop/laptop & mobile. If I understand correctly, this may give GrapheneOS users access to some desktop/laptop only apps when desktop/laptop not available.

that there has to be seperate OS's for mobile than desktop just shows how far open source has yet to go in the future...but yea...it's definitely a big divider when coding something new....what hardware target market are you aiming for is a pretty big split right at the start.