I say this as a joke, yet: https://www.npmjs.com/package/react-unity-webgl
Simply rendering your Unity Application within your React Application is just the beginning! The Unity Context exposes a lot more fun functions and properties to play around with such as two way communication or requesting fullscreen or a pointerlock. The possibilities are endless, what's next is up to you!
Love it or hate it. Everything ends up in JavaScript!Lowering the bar of participation greatly increases the amount of shit that is created, but also increases the amount of exceptional examples which can come from a domain. If 80% of everything created is almost complete garbage, then lowering the bar of entry for participating will exponentially increase the amount of shit out there. But it will also enable a few really great apps which wouldn't have existed otherwise. I think we need better filtering than to raise the bar so only true experts can participate.
As a language for new developers is terrible: 100 different ways to do anything, most of them a muddle of paradigms that's inexplicable to anyone without 2 decades of experience, and so on.
Imagine a new developer using ChatGPT to generate: python, C, go, etc. vs. generating javascript. Most of the generated js is incomphrensible to newbies, but for the others generally obvious.
But applets were doing a lot more in the 90's and Flash dominated into the 2010s. However you feel about JS today, it's difficult to say it was all "first-mover advantage".
And Java applets with their loading times and dependence on the visitor having Java installed ... nah, not really a competitor.
> The biggest innovation with Vision Pro is visionOS. visionOS provides native app frameworks, so developers can build apps for it. That sounds ridiculously obvious, and yet its something Meta have failed to offer for years. Every app on Quest has to reinvent how buttons work, how a scroll view works, how far away from the user the content should be etc.. and every app works differently. On visionOS, all of this is handled by Apple, and every app looks and feels the same.
Meta does have standardized utilities for translating movement to touch/drag/etc. interactions on arbitrary virtual surfaces:
https://developers.facebook.com/blog/post/2022/11/22/buildin...
https://developer.oculus.com/documentation/unity/unity-isdk-...
But it doesn't seem (AFAIK) to answer the other side of this, which is the UI design system so apps have a consistent look and feel. Which is perhaps more common coming from a game development perspective, but ever since the Mac OS shareware days, Apple's understood that it's empowering to a certain kind of developer if you make it easy/the default path for them to build experiences that match a standardized look and feel. I'm honestly surprised that Meta didn't at least make an optional SDK for this.
https://developer.oculus.com/documentation/native/android/mo...
I truly don't get it.
https://reactnative.dev/blog/2021/08/26/many-platform-vision
if your goal is to make some sort of `spatial computing` tool, well there nothing here you can use. each app is it's own little silo that has little room for interaction. I'd love to be able to write my own custom apps that can exist in the home screen/environment and that can interact with each other in non trivial ways. it would make it feel more like a personal space rather than a 3D slideshow that I can use to launch games.