4 ms·

This licensing does not apply to enterprise editions and volume licensing, I believe you are still looking at consumer market which Microsoft already lost to a

This licensing does not apply to enterprise editions and volume licensing, I believe you are still looking at consumer market which Microsoft already lost to a Apple and lately google chromebooks. The major revenue stream for Microsoft is still old long term licensing deal for office combined with windows and than related server technologies to support office applications. The model changed from licensing+upgrade fee to new subscription fees. This can be office 360 subscriptions which get you office products and windows or volume license subscriptions. Depending on the type of subscriptions these are classified as cloud or windows and office revenue. Azure come into picture as those companies having volume licenses have applications in legacy .NET which they move to Azure. Microsoft is supporting Linux today because they lost the battle of technical superiority and most of the azure workloads for supporting internal business apps run on Linux. They ported .NET to Linux just to have those old accounts do not move out of azure and Microsoft proprietary eco-system easily and move them to subscription with long term contracts. Majority of the revenue effect you see is just because Microsoft abandoned product updates for old versions and forced customers to move to windows 10 and above by making old one economically very expensive. So Nadella was lucky because he got the benefit of the cyclical revenue increase due to enterprise upgrades which companies didn’t do for many years. Obviously adoption of Linux as primary driver for Azure kept those old customers from moving out of Azure to Amazon or google, even though technically azure quality and services were inferior. A company will not move to amazon or google unless there is significant exponential gains. If the old vendor can still support and give something which is not bad but not the best, customer will still stay on and here Nadella was good not to bash Linux like Balmer.

scarface74 7y ago
It’s just as easy to move .Net Framework workloads to AWS as it is to Azure.
- dragonsh 7y ago
  Companies prefer to purchase services within an established contract than to go ahead and sign a new one with new provider and go through the bidding process. Also .Net is synonymous with microsoft so there is no reason to trust AWS, it's not their priority, they are a Perl and Java shop in general.
  - scarface74 7y ago
    AWS is always bragging that they have twice as many Windows VMs than Azure. AWS a Perl shop? All of AWS services treat C# .Net Core as a first class citizen. - CodeBuild has prebuilt C# .Net Core images for building apps. For licensing reasons they don’t have prebuilt Windows/Framework containers but their instructions are so clear that I was able to build one before I knew anything about Docker - Lambda has native support for .Net Core 2.x and the C# SDK for AWS has a template to build a custom runtime for C# 3.x - Speaking of which, the AWS SDK and plug-in for C#/Visual Studio and the corresponding Nuget packages are excellent and fully featured. - The CloudFormation Developer Kit supports C# - There are CodeStar and ElasticBeanstalk getting started templates for .Net Framework and .Net Core What are they missing?
    - dragonsh 7y ago
      AWS was built to support Amazon website which is built in Perl and still internal AWS core code might contain perl. Probably over the years they might have moved slowly to Java. I don't work for AWS so can't say much. Regarding support for .NET whatever AWS does microsoft will always be way ahead of them. Microsoft is not elastic.co that AWS leech on and put the original guys on the side and don't contribute back. AWS is really like a leech on open source now trying to leech on Kubernetes. They can do this with small open source project, not with the projects supported by google or Microsoft. Like when it comes to Kubernetes AWS is playing catch with Google. So AWS Fargate and other services are still inferior to Google managed K8s. Indeed microsoft at present is ahead of AWS in managed kubernetes services. Its just the initial head-start and developers who are familiar with AWS proprietary API's find it hard to believe that in such a short time the skills they learned is no longer cutting edge and google or microsoft proprietary API's overtaken them in performance and ease of use.
      - throwaway2048 7y ago
        AWS was never built to support amazons website, it was never the result of amazon.com's internal code-base of "hosting" getting made public, it was never amazon's excess peak server capacity, etc, it had virtually no relation to the hosting of amazon.com at all, it was an independent project that might have benefited from a lot of the general design principles of how amazon.com was built, but that is it. All of these things are widely believed myths that have little to no basis in reality. It certainly was not designed as some kind of Perl hosting environment. It didn't even host Amazon.com at all until many years after the fact.

scarface74 7y ago

It’s just as easy to move .Net Framework workloads to AWS as it is to Azure.

dragonsh 7y ago
Companies prefer to purchase services within an established contract than to go ahead and sign a new one with new provider and go through the bidding process. Also .Net is synonymous with microsoft so there is no reason to trust AWS, it's not their priority, they are a Perl and Java shop in general.
- scarface74 7y ago
  AWS is always bragging that they have twice as many Windows VMs than Azure. AWS a Perl shop? All of AWS services treat C# .Net Core as a first class citizen. - CodeBuild has prebuilt C# .Net Core images for building apps. For licensing reasons they don’t have prebuilt Windows/Framework containers but their instructions are so clear that I was able to build one before I knew anything about Docker - Lambda has native support for .Net Core 2.x and the C# SDK for AWS has a template to build a custom runtime for C# 3.x - Speaking of which, the AWS SDK and plug-in for C#/Visual Studio and the corresponding Nuget packages are excellent and fully featured. - The CloudFormation Developer Kit supports C# - There are CodeStar and ElasticBeanstalk getting started templates for .Net Framework and .Net Core What are they missing?
  - dragonsh 7y ago
    AWS was built to support Amazon website which is built in Perl and still internal AWS core code might contain perl. Probably over the years they might have moved slowly to Java. I don't work for AWS so can't say much. Regarding support for .NET whatever AWS does microsoft will always be way ahead of them. Microsoft is not elastic.co that AWS leech on and put the original guys on the side and don't contribute back. AWS is really like a leech on open source now trying to leech on Kubernetes. They can do this with small open source project, not with the projects supported by google or Microsoft. Like when it comes to Kubernetes AWS is playing catch with Google. So AWS Fargate and other services are still inferior to Google managed K8s. Indeed microsoft at present is ahead of AWS in managed kubernetes services. Its just the initial head-start and developers who are familiar with AWS proprietary API's find it hard to believe that in such a short time the skills they learned is no longer cutting edge and google or microsoft proprietary API's overtaken them in performance and ease of use.
    - throwaway2048 7y ago
      AWS was never built to support amazons website, it was never the result of amazon.com's internal code-base of "hosting" getting made public, it was never amazon's excess peak server capacity, etc, it had virtually no relation to the hosting of amazon.com at all, it was an independent project that might have benefited from a lot of the general design principles of how amazon.com was built, but that is it. All of these things are widely believed myths that have little to no basis in reality. It certainly was not designed as some kind of Perl hosting environment. It didn't even host Amazon.com at all until many years after the fact.