4 ms·

So Apple could have done this, but did not. Why? (Speculation and leaks welcome) - [Profit on basic innovation] Did they want to wait and see how their custome

by ncr100 3y ago

So Apple could have done this, but did not. Why? (Speculation and leaks welcome) - [Profit on basic innovation] Did they want to wait and see how their customers would adopt VisionOS's native free-floating windows, so as to avoid cognitive overload by commingling with MacOS windows? - [Benevolence to fellow competitors] Did they not want to takeover the existing market of virtualized VR desktops?

theultdev 3y ago
Most likely because it wasn't polished, so get it out now in a polished and limited state and now you have a fancy update to tout when it is done.
realslimjd 3y ago
I'm reasonably certain it's a combination bandwidth and tech issue. The Vision Pro is effectively using AirPlay to mirror the whole screen. If you used AirPlay to mirror each window as a whole screen, you'd run out of bandwidth pretty quickly. The windowing system in MacOS, Quartz Compositor, also isn't built to stream window information. Right now it has a big built in assumption that any windows its displaying are on a screen it also controls. It was probably too big a lift across teams to also re-write the graphics stack for MacOS for the launch of the Vision Pro. Hopefully they get it working in the future, but neither of these problems are easy to solve.
- NoPedantsThanks 3y ago
  [dead]
- ncr100 3y ago
  Makes a lot of sense, future will solve it someday.