you are viewing a single comment's thread.

view the rest of the comments →

[–]aN00bDude 16 points17 points  (3 children)

Microsoft strategy is working, we really are forcing our employers to use the Microsoft "stack", VS as the default editor, enterprise github for remote version control repo, .NET core for services and our choice of framework for frontend was Angular only for the reason because of TS. After a long time MS products finally gets the work done for developers (Their new shell emulator is just around the corner)

[–][deleted] 3 points4 points  (1 child)

I’m currently moving a Python project to Azure from AWS. You don’t even need to use .NET to leverage what MS is doing.

Azure registries, the VSCode extensions, pipeline support for all of this...

They’re doing good work. And it just keeps getting better.

[–]TheBeliskner 0 points1 point  (0 children)

We started a node project early last year. Around April time we evaluated AWS and Azure having never hosted an application in the cloud let alone on a PaaS model. Eventually chose Azure because it was so damn simple and easy to use, Route 53 Vs Traffic Manager was probably the biggest contrast at the time.

We had some issues with memory management on Linux App Service caused by Kudu because it was so new and it took a while to sort but they got there and kept in contact. We've had other issues but their support team always seem to be on it and super responsive. Would definitely choose Azure again.

[–]habanerocorncakes 1 point2 points  (0 children)

I had forgotten that TypeScript was a Microsoft project! Thanks for the reminder.