2 ms·

The author has no point, and this post is riding some kind of geek activism vibe. The author complains that they couldn't use C++ on the iPhone or iPad, even t

by 7e 3y ago

The author has no point, and this post is riding some kind of geek activism vibe. The author complains that they couldn't use C++ on the iPhone or iPad, even though you can. They then complain that the Vision Pro isn't "open" but don't define what they mean. You can certainly write C++ application software the Vision Pro (see https://babylonjs.medium.com/building-babylon-native-for-the-apple-vision-pro-8c580cc73041 https://babylonjs.medium.com/building-babylon-native-for-the...). I think they're complaining about Swift for the UI, but it's hard to tell. Maybe they're complaining that the SDK does too much for you.

Guvante 3y ago
Apple is severely limiting what access software has to data from the device. And that even includes your own software. The point is messing around with cool technology is a great way to engage with things.
arjonagelhout 3y ago
The main point I tried to make, but apparently muddied through subpar writing, was that visionOS ultimately is an operating system more akin to iPadOS than macOS, which I think ultimately results in people being less able to deeply understand the inner workings and of the computer. An iOS-like operating system aims to abstract away file systems, how software runs and leaves the user merely running apps. You can use a code editor to write code on iOS or iPadOS, but you wouldn’t be able to run that software outside of that code editor on the device. You couldn’t use it to build an application binary / executable with it to be run directly on the device. I did not aim to make any points about the development experience for building apps for the Vision Pro. Rather about the restrictive nature of the operating system when using the Vision Pro as a primary computing device. As mentioned elsewhere, next time I’ll make the post more informative and less a quick “does anyone else feel this way too?”, as I see that this does not fit the standards of the HN audience.

by 7e 3y ago

Guvante 3y ago

Apple is severely limiting what access software has to data from the device. And that even includes your own software. The point is messing around with cool technology is a great way to engage with things.

arjonagelhout 3y ago

The main point I tried to make, but apparently muddied through subpar writing, was that visionOS ultimately is an operating system more akin to iPadOS than macOS, which I think ultimately results in people being less able to deeply understand the inner workings and of the computer. An iOS-like operating system aims to abstract away file systems, how software runs and leaves the user merely running apps. You can use a code editor to write code on iOS or iPadOS, but you wouldn’t be able to run that software outside of that code editor on the device. You couldn’t use it to build an application binary / executable with it to be run directly on the device. I did not aim to make any points about the development experience for building apps for the Vision Pro. Rather about the restrictive nature of the operating system when using the Vision Pro as a primary computing device. As mentioned elsewhere, next time I’ll make the post more informative and less a quick “does anyone else feel this way too?”, as I see that this does not fit the standards of the HN audience.