You may not find a use for it, and neither do I in my workflow. But think about accessibility - it might enable some users to perform tasks the find physically difficult using just their voice.
Or, you can go get a beer or a [slice of] pizza, and call out to vscode from across the room to build your app or start a server or something.
Indeed - users that need accessable features should not rely on each piece of software they use to supply them. But even as a one-off feature, it is a good thing to have IMO, as it will certainly expose APIs and hooks in vscode for other accessibility software to utilize.
3 Comments
cosmic_slate@dmv.social · 5 pts · 2y
malockin@lemmy.world · 6 pts · 2y
You may not find a use for it, and neither do I in my workflow. But think about accessibility - it might enable some users to perform tasks the find physically difficult using just their voice.
Or, you can go get a beer or a [slice of] pizza, and call out to vscode from across the room to build your app or start a server or something.
cosmic_slate@dmv.social · 3 pts · 2y
malockin@lemmy.world · 3 pts · 2y
Indeed - users that need accessable features should not rely on each piece of software they use to supply them. But even as a one-off feature, it is a good thing to have IMO, as it will certainly expose APIs and hooks in vscode for other accessibility software to utilize.
Also, open source, learning, and all that jazz.
Plasma@lemmy.ml · 2 pts · 2y
I don't even get why companies are pushing "AI" tools, what do they think they'll accomplish by doing so?
cosmic_slate@dmv.social · 0 pts · 2y
NostraDavid@programming.dev · 4 pts · 2y