rbd765

The AVP is an incredible device, but it's too restrictive and the 3D spectacle doesn't offset the myriad of issues that I've run into:

- If I want to watch movies, I'll typically do so with my wife, on my 4K smart TV. The AVP is not a shared experience unless you purchase an additional unit.

- The virtual display can't be used with arbitrary devices (e.g. PS5, PC, Raspberry PI) via direct HDMI, only over network streaming, which has latency/quality constraints.

- The passthrough quality is not good enough to do anything non-trivial.

- The native Vision Pro apps tend to be neutered compared to the MacOS equivalent.

- When flying, it's a bit too bulky to take as carry-on, unless you dedicate your entire backpack to it or carry by hand.

From a development standpoint, I found that the SDK was quite shallow and didn't provide as much hardware access as I would have liked– particularly the raw camera feed. Apparently there's now an enterprise program that unlocks access, but you have to jump through some hoops and get manually approved, which is too much friction. Additionally, the market is quite weak. I had my app get featured in the App Store a year ago and hardly made enough profit to justify further time investment.

If there was a Linux equivalent to the Vision Pro that didn't require a social media account, I'd be more receptive. The biggest issue across modern AR/VR devices is the tendency towards closed ecosystems and lack of integration with external devices. For now, my AVP is largely collecting dust on the shelf until I get bored on a random Sunday afternoon and decide to see what's new.

The ecosystem of web standards, browsers and search engines is mostly optimized with MPAs in mind. That's the base experience for web. Things have only gotten more complicated as we've built abstractions on top of MPAs.

In the earlier iterations, SPAs broke navigation, broke SEO, had no decent state management solution, and required a good understanding of reflow/repaint to avoid performance issues.

The ergonomics of SPA frameworks has improved drastically and metaframeworks like Next.js have mostly fixed those issues. But the myriad of options and paradigms might be exhausting for some devs.

Some experienced devs might be nostalgic for the document-centric PHP days. I imagine that many newer devs have only recently been exposed to the pleasure of building a simple MPA website, as they were initially thrust straight into React.

For example, I recently chose to use Hugo for my blog. Just wanted something dead simple to build a static website without all the bells and whistles of a SPA.