Live data from Hacker News

Remote-Powered Developer Tools

devblogs.microsoft.com

71–80 of 136 posts

Re: Remote-Powered Developer Tools

#71

Hey all! I’m the author of this post, and lead the PM team at Microsoft behind IntelliCode, Live Share, and the cloud-based remote development capabilities described in this article. We’re looking forward to working with developers, and learning how to further support teams who are looking to up-level their productivity and embrace further workplace flexibility (yay for remote development!). In the meantime, feel fre…

I'm interested in the privacy aspect of online.visualstudio.com. if I use it, does my code get tunneled through Microsoft's servers? Or is it end to end encrypted or something else?

Re: Remote-Powered Developer Tools

#72
post #61

It's worth noting that the new VS Code Remote Development extensions are not open source, which means that it is impossible for the community to fix bugs, and add new platforms/environments/features, or see the code that's running in their environment without reverse engineering. https://code.visualstudio.com/docs/remote/faq#_why-arent-the...

Thanks for pointing that out. (Also odd formulation of the question: "Why aren't the open soure? - We made the decision to keep them closed source." The actual answer is to the next question: "we may provide premium developer services.")

Specially since there are already open-source alternatives:

https://github.com/cdr/code-server

Re: Remote-Powered Developer Tools

#73
post #31

I can see more developers adopting a cloud-based IDE. There may be desktop apps, which will be Electron or PWAs (if the APIs ever evolve enough), but the environment will be fully remote. The benefit is all the set up will already be done: the IDE will provide all the same code formatting, linting, dev sandbox, environment configuration, debugging profiles. No set up of any tooling to make this work. New employees ca…

Some possible upsides certainly, but you don't see any downsides?

Lock-in leading to price hikes/interfaces changing at MS's whim/global outages of the services/loss of control over your own code/loss of network activity/being locked out for an arbitrary period because of payment errors or accidents/others.

I've had my chain yanked a few times and I don't trust any large company.

I can afford to spend a day unbreaking my machine (annoying though it is), commercially it just seems safer.

Re: Remote-Powered Developer Tools

#74

Hey all! I’m the author of this post, and lead the PM team at Microsoft behind IntelliCode, Live Share, and the cloud-based remote development capabilities described in this article. We’re looking forward to working with developers, and learning how to further support teams who are looking to up-level their productivity and embrace further workplace flexibility (yay for remote development!). In the meantime, feel fre…

Our team has been using remote VS Code to build our project on Azure Confidential Compute VMs. The tool is amazing, and is a massive improvement over all other remote dev solutions we’ve tried. Thank you!

Re: Remote-Powered Developer Tools

#75
post #14

Is there any way to run Atom in a browser? I know this question sounds silly since it's basically a browser, but that it actually is similar to c9.

Serious question: Why prefer Atom over VSCode?

From my evaluations early on in both they seemed like the same thing but VSCode had more features (esp. built-in terminal) and performed significantly better.

I'm sure that there's been a lot of progress in the years since, but I haven't kept up.

I could see not trusting Microsoft with an open source project, but now that they own Github they have two open source Electron-based code editors, and I can't imagine that's going to last for long. So really I'd be more concerned for the long term health of Atom than VSCode.

Re: Remote-Powered Developer Tools

#76
FWIW, I wrote a small script for remote dev called duplexrsync, love it so far. https://github.com/francoisp/DuplexRsync Haven’t tested on win10 yet but it should work, no language limitations and it’s 150 lines of open source MIT bash. EDIT: il someone tests this on win10’s Ubuntu sidecar thing before me, and if there’s a glitch besides the calls to homebrew that can be made optional, please send a PR! Cheers and the peace be with you!

Re: Remote-Powered Developer Tools

#77
post #61

It's worth noting that the new VS Code Remote Development extensions are not open source, which means that it is impossible for the community to fix bugs, and add new platforms/environments/features, or see the code that's running in their environment without reverse engineering. https://code.visualstudio.com/docs/remote/faq#_why-arent-the...

Thanks for pointing that out. (Also odd formulation of the question: "Why aren't the open soure? - We made the decision to keep them closed source." The actual answer is to the next question: "we may provide premium developer services.")

After embracing open source, they appear to now be extending it...

Re: Remote-Powered Developer Tools

#78

As an "oldtimer", I tried out AWS Cloud9 and other cloud based IDEs and came away deeply unimpressed . However my frame of reference was to my experience with my heavily customized IDEs. However, my daughter's classroom uses only online IDEs. I think they got used to this style of IDEs when they got started with Scratch programming in elementary school. These kids are much more comfortable and productive on the onlin…

Same (kids in Virginia Beach School system) - they've standardized on Chromebooks so it makes sense.

Re: Remote-Powered Developer Tools

#79

It's worth noting that the new VS Code Remote Development extensions are not open source, which means that it is impossible for the community to fix bugs, and add new platforms/environments/features, or see the code that's running in their environment without reverse engineering. https://code.visualstudio.com/docs/remote/faq#_why-arent-the...

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.

Re: Remote-Powered Developer Tools

#80
post #14

Is there any way to run Atom in a browser? I know this question sounds silly since it's basically a browser, but that it actually is similar to c9.

Serious question: Why prefer Atom over VSCode? From my evaluations early on in both they seemed like the same thing but VSCode had more features (esp. built-in terminal) and performed significantly better. I'm sure that there's been a lot of progress in the years since, but I haven't kept up. I could see not trusting Microsoft with an open source project, but now that they own Github they have two open source Electro…

Good question!

I prefer Atom because I use it since the early days and I am so used to it. The whole workflow is super awesome and everything is simple and clean. I don't have any performance problems nowadays (this was a big problem years ago) so I have zero complaints.

It's hard to switch, I tried VSCode, don't like it and have no reason to switch because _for me_ Atom just works and I love it.

Post reply on HN