▲ | wkat4242 2 days ago | |||||||
Very interesting. I do have a bit of a "vids or it didn't happen" feeling about this. Cool idea to use your own kernel though it does sound like you could find yourself in perpetual development hell. And, don't forget all the sufficiently powerful SoCs are super closed. You won't be able to leverage any of their existing driver work and you will need some serious clout to get access to their documentation, with some really scary NDAs attached. However I'm sure you know this and took it into account. Very cool. I hope you will manage to get it to market! | ||||||||
▲ | ayush_xeneva a day ago | parent | next [-] | |||||||
Thank you for your comment and yes we totally get the things that you've mentioned. We're well prepared and ready to tackle a possible "perpetual development hell" and are also aware about the issues with closed source SoCs. It's quite a challenging route and journey but we do not intend on looking back and are sure about figuring out things one way or the other. Coming to the "vids or it didn't happen" feeling, we totally get that as well. To be fair, we would've had the same feeling if we watched ourselves from a third person perspective. But we're actively working on bringing visible proof (benchmark is a better work) on the claims and promises that we're making. And in your analogy, the vids are coming soon, stay tuned ;) | ||||||||
▲ | sdallagasperina 2 days ago | parent | prev [-] | |||||||
This is a huge point. Even if you write the perfect kernel, the reality is that XR hardware is tied up in vendor drivers and NDAs. Without access to those, you end up reinventing the easy part while still locked out of the hard parts. Curious if the team has a strategy for this, or if the kernel is mainly a sandbox for now. | ||||||||
|