If they manage to pull something like this off and be first to market I guess Magic Leap, HoloLens, and whatever Meta is cooking up (if they still are doing something in that space anyway) will very likely be pretty much dead, by the way.
Ask HN: What would an IDE built for the Apple Vision Pro look like?
11–20 of 50 posts
Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#12But in all seriousness, you can have a tree of small code windows connected by various dependencies. So it will be much easier to see a piece of code and it’s uses / definitions, and thus understand a codebase’s architecture
Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#13Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#14just look at what IDEs that runs exclusively on ios are like: crap. nobody invest into a closed platform. i expect jetbrains to came up with something marvelous for ar/vr, but it will run on the upcoming version of Microsoft or HP glasses. you know, the only ones today that works just like an external monitor without a locked in ecosystem like apple or facebook. the silly apps and games and such will net millions tho…
Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#15Most programming work is still text editing with various amounts of debugging, refactoring, and autocompletion. It is not obvious to me how an AR interface would make a difference other than more virtual screen real estate. You would still need a way to enter text, build code, run tests, etc. This means a keyboard and pointing device (mouse, trackpad, etc.) are still needed unless something else can do it better. Gra…
Text no longer needs to be the primary way of conveying programs. There are practical reasons text works best on screens, but if your coding environment is boundless then there’s no reason to believe you can’t do fancier things like direct manipulation of ASTs pretty easily. Imagine "grabbing" an AST node and attaching it to a different parent, all in space.
Beyond simple AST manipulation, the Vision Pro will probably enable Dynamicland-esque "programming spaces" where you manipulate objects in your virtual environment to construct programs.
Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#16More open windows. But in all seriousness, you can have a tree of small code windows connected by various dependencies. So it will be much easier to see a piece of code and it’s uses / definitions, and thus understand a codebase’s architecture
Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#17Most programming work is still text editing with various amounts of debugging, refactoring, and autocompletion. It is not obvious to me how an AR interface would make a difference other than more virtual screen real estate. You would still need a way to enter text, build code, run tests, etc. This means a keyboard and pointing device (mouse, trackpad, etc.) are still needed unless something else can do it better. Gra…
> Most programming work is still text editing [...] Text no longer needs to be the primary way of conveying programs. There are practical reasons text works best on screens, but if your coding environment is boundless then there’s no reason to believe you can’t do fancier things like direct manipulation of ASTs pretty easily. Imagine "grabbing" an AST node and attaching it to a different parent, all in space. Beyond…
Re: Ask HN: What would an IDE built for the Apple Vision Pro look like?
#18I would expect extracting out more of the meta-logic via GPT, and showing relevant panes dynamically. If you get an error, automatically search for the answer and propose the change. If you add a new flow uncovered by tests, propose the test. Generally, have panes that are dynamic to what you are doing, and tightly couple them. I could imagine looking at different zoom levels of a code file, folder, or architecture,…