Remote-Powered Developer Tools
81–90 of 136 posts
Re: Remote-Powered Developer Tools
#82It'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.
Source Open Dumped, not Open Sourced. Open source product is a journey, not only just a destination.
Re: Remote-Powered Developer Tools
#83As 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…
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.
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
Re: Remote-Powered Developer Tools
#84Hey 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…
Re: Remote-Powered Developer Tools
#85Re: Remote-Powered Developer Tools
#86Earlier quoted context omitted.
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.
Glad to hear the performance now is better now than it was back then!
Re: Remote-Powered Developer Tools
#87Re: Remote-Powered Developer Tools
#88good! now they will have my code
Re: Remote-Powered Developer Tools
#89It's a great experience right now, but I pretty often end up pulling the repository down just for Go To Implementation.
Re: Remote-Powered Developer Tools
#90Earlier quoted context omitted.
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...