Earlier quoted context omitted.
We’re enabling a browser-based experience because of the convenience and accessibility it can provide (e.g. running on an iPad Pro), but we’re also building remote development tools for Visual Studio and Visual Studio code, to ensure that folks can choose the right tools for them, and reap the same benefits of multi-machine portability, reduced setup, and anywhere access.
>>“running on an iPad Pro” I was under the impression that browser based IDE won’t work on iOS because safari (or maybe UIkit) doesn’t support some type of controls. I can’t find the mention but I read that here at HN not long ago
Remote-Powered Developer Tools
101–110 of 136 posts
Re: Remote-Powered Developer Tools
#102Re: Remote-Powered Developer Tools
#103Earlier quoted context omitted.
At Pycon, I spoke with a couple of people at Microsoft who insisted that it would be eventually. They were not, however, on the VS Code team, and speaking unofficially. At the booth, the VS Code people said that the reason it was closed was because it fell into the "services" umbrella, which has a lot of closed-source components. They did not have a comment on if it was going to be opened.
>who insisted that it would be eventually Source Open Dumped, not Open Sourced. Open source product is a journey, not only just a destination.
Re: Remote-Powered Developer Tools
#104Anyone know if there will be an on-premises option for this? I'd love to have this but for various reasons we'd have to run it off our own servers.
Re: Remote-Powered Developer Tools
#105- StackBlitz: https://stackblitz.com/
- Theia: https://www.theia-ide.org/
- Coder: https://coder.com/
Overall, this is a prime example of one of the synergies that Microsoft was able to create from the GitHub acquisition which was the missing puzzle piece. Microsoft now has control over a complete software development pipeline: a development platform (Windows), an IDE (vscode, vs), a code versioning host (GitHub), continuous integration (Azure Pipeline), deployment (Azure).
If Microsoft can leverage its control over this complete chain to make the whole experience integrated and effortless as it's doing with Visual Studio Online here, it could well take over the market, especially in corporate environments.
Re: Remote-Powered Developer Tools
#106Re: Remote-Powered Developer Tools
#107Re: Remote-Powered Developer Tools
#108Earlier quoted context omitted.
After embracing open source, they appear to now be extending it...
That's the exact thing I thought with this. How are they that without a clue as to the world right now when they do stuff like this?
Re: Remote-Powered Developer Tools
#109What is Microsoft's motivation for putting so much effort into VSCode? I don't understand the business of this particular product, and it makes me kind of uneasy.
B) Gaining developer mindshare is very powerful. If you want another example of how powerful this is, just look at the dominance of Windows XP and Windows 7 in the developer market, which in turn, made a huge proliferation of software available for the windows eco system. They are basically getting developers to dogfood the OS and developer tools for them.
3) Microsoft can learn from how people use visual code and make the developer experience overall much more pleasant for their azure integrations. You get enough developers telling the C-Suite how awesome Azure is, pretty soon you are going to have companies switching off AWS to Azure because "it integrates so well with all the developer tooling I am already using"(<--- Which would be VS Code.)
Re: Remote-Powered Developer Tools
#110Is this limited to only Linux and MacOS being the host via OpenSSH here?