3 ms·

I think the lock in using API or platform is no longer necessary. Their well-integrated services in terms of safety, security, ease of use and reliability will

by harigov 10y ago

I think the lock in using API or platform is no longer necessary. Their well-integrated services in terms of safety, security, ease of use and reliability will sell on their own. The most important computing battle is on the cloud - get developers to build their tools using MS technologies and then provide much better performance and integration on Azure. If open source implementation of .NET CLR is 10% slower than the one on the cloud, they are saving users 10% in revenue by running it on Azure. I believe Visual Studio Code was supposed to be a website. I think they may have figured out that the web isn't ready yet for such functionality and ended up with a compromise. I can see a future where they are going to include VS code along with all VS online services including deployment automation to Azure through a single web portal. All your software development/deployment/management needs will be taken care of by MS.

erikbye 10y ago
VSCode was not supposed to be a "website". VSCode is based on Monaco, the editor for Visual Studio Online. https://github.com/Microsoft/monaco-editor https://github.com/Microsoft/monaco-editor
mattmanser 10y ago
But, speaking from experience and lots of recent discussion recently here, Azure doesn't have performance or ease of use. The very people using Azure are the people MS are going out to burn with all this focus on the new stuff, the people invested in their stack are getting heavily burnt by churn and the substandard performance of .net core. One of the great things about C#/ASP.Net is that it was improving constantly, they've basically put that on hold for 2-4 years while they try and support linux. And for what? ASP.Net/C# was basically a much faster, better tooled, statically typed Rails. There was a discussion here of what all the HN startups were using the free azure credits for and the consensus was basically "anything non-critical, log parsing, azure is terrible". One of the GCE guys replied to one of my comments about consistent latency of 3-5ms between website instances and SQL instances on azure with basically "ours is much better, 100ns latency, we're now beta-ing SQL Server". With .net core MS have basically opened up the C# space to be eaten by AWS + GCE. And the recent terrible re-write of Azure web interface hasn't got anyone's hopes up of improvements any time soon.

by harigov 10y ago

erikbye 10y ago

VSCode was not supposed to be a "website". VSCode is based on Monaco, the editor for Visual Studio Online. https://github.com/Microsoft/monaco-editor https://github.com/Microsoft/monaco-editor

mattmanser 10y ago

But, speaking from experience and lots of recent discussion recently here, Azure doesn't have performance or ease of use. The very people using Azure are the people MS are going out to burn with all this focus on the new stuff, the people invested in their stack are getting heavily burnt by churn and the substandard performance of .net core. One of the great things about C#/ASP.Net is that it was improving constantly, they've basically put that on hold for 2-4 years while they try and support linux. And for what? ASP.Net/C# was basically a much faster, better tooled, statically typed Rails. There was a discussion here of what all the HN startups were using the free azure credits for and the consensus was basically "anything non-critical, log parsing, azure is terrible". One of the GCE guys replied to one of my comments about consistent latency of 3-5ms between website instances and SQL instances on azure with basically "ours is much better, 100ns latency, we're now beta-ing SQL Server". With .net core MS have basically opened up the C# space to be eaten by AWS + GCE. And the recent terrible re-write of Azure web interface hasn't got anyone's hopes up of improvements any time soon.