4 ms·
I find a couple things pretty neat here: 1 - All of the screenshots are from a Mac. This never would have happened with the old MSFT. 2 - The performance of t
by MR4D 5y ago
I find a couple things pretty neat here:
1 - All of the screenshots are from a Mac. This never would have happened with the old MSFT.
2 - The performance of this is pretty good. Admittedly, I just played with this for a couple minutes, but even opening a folder with a bunch of files was snappy.
- dustinmoris 5y agoThis is because Microsoft doesn't seem to want Windows developers to use VS Code. They want to keep them locked into Visual Studio and Windows Azure, which is why the C# plugin is one of the worst from all language plugins in Code.
- jaywalk 5y agoThat's a pretty strange implication. I just tried opening up a .NET Core application in VS Code developed exclusively in Visual Studio, and it fired right up. Now I certainly wouldn't say that the debugging experience is as good as VS, but nobody should expect it to be. VS Code isn't supposed to be a replacement for VS, although it can certainly hold it's own. And it's free.
- imafish 5y agoVS community is also free :)
- jaywalk 5y agoYes, but it has a very significant licensing restriction that prevents it from being used to develop commercial software. VS Code has no such restriction.
- jongalloway2 5y agoA little oversimplified - Visual Studio Community can be used to develop commercial software, with restrictions to (summarizing) 5 conccurrent users in non-enterprise organizations. https://visualstudio.microsoft.com/license-terms/mlt031819/ https://visualstudio.microsoft.com/license-terms/mlt031819/
- WorldMaker 5y agoMicrosoft has long been one of the biggest application vendors on the Mac, there were previous eras where most of the screenshots of Office would have been taken on a Mac too. Though yes, never would have happened in the "Windows is our sports team, hoo rah" parts of the Ballmer era.