3 ms·

How are VS Code and GitHub about driving traffic to Azure?

by yyhhsj0521 7y ago

streetcat1 7y ago
For VSCode, I think that Microsoft is introducing extensions for specific MS services. For exmaple, you can run ML experiminets directly from VSCode. I would expect VSCode to slowly become azure services UI. For GitHub, Look at the steps from the acquisition forward. For example, github actions is a CI/CD run on azure. Next step would be a gitops service that will integrate with AKS. Etc.
- flurdy 7y ago
  > Next step would be a gitops service that will integrate with AKS That means Weaveworks swallowed up soon then[1], with its Flux GitOps for Kubernetes[2]. [1] https://www.weave.works/ https://www.weave.works/ [2] https://fluxcd.io/ https://fluxcd.io/
mmcnl 7y ago
I think VS Code and GitHub are mainly about branding and building a new reputation. Microsoft provides first-class development tools (VS Code and GitHub) to millions of developers every day now. Once this becomes the new normal to developers, Azure easily becomes a serious contender for running your applications as well.
davnicwil 7y ago
First class, built in integrations. While an open API is offered so anything can be integrated, nothing is going to beat custom built in integrations for user experience. Also, built in integrations are always a step ahead in terms of time to market too. Even if only by a few weeks or months, this really matters. The example I'd point out is integration of Typescript vs Flowtype in VSCode. The Flowtype plugin maintained by the community was a good effort, but was always quite a way behind the native Typescript integration. There are more reasons for this than just technical, obviously, but that's one of the main ones. I think, having been a user of both, the awesome native VSCode integration was a huge factor in Typescript 'beating' Flowtype. It'd be a similar idea for Azure too.

3 ms·

How are VS Code and GitHub about driving traffic to Azure?

by yyhhsj0521 7y ago

How are VS Code and GitHub about driving traffic to Azure?

streetcat1 7y ago
For VSCode, I think that Microsoft is introducing extensions for specific MS services. For exmaple, you can run ML experiminets directly from VSCode. I would expect VSCode to slowly become azure services UI. For GitHub, Look at the steps from the acquisition forward. For example, github actions is a CI/CD run on azure. Next step would be a gitops service that will integrate with AKS. Etc.
- flurdy 7y ago
  > Next step would be a gitops service that will integrate with AKS That means Weaveworks swallowed up soon then[1], with its Flux GitOps for Kubernetes[2]. [1] https://www.weave.works/ https://www.weave.works/ [2] https://fluxcd.io/ https://fluxcd.io/
mmcnl 7y ago
I think VS Code and GitHub are mainly about branding and building a new reputation. Microsoft provides first-class development tools (VS Code and GitHub) to millions of developers every day now. Once this becomes the new normal to developers, Azure easily becomes a serious contender for running your applications as well.
davnicwil 7y ago
First class, built in integrations. While an open API is offered so anything can be integrated, nothing is going to beat custom built in integrations for user experience. Also, built in integrations are always a step ahead in terms of time to market too. Even if only by a few weeks or months, this really matters. The example I'd point out is integration of Typescript vs Flowtype in VSCode. The Flowtype plugin maintained by the community was a good effort, but was always quite a way behind the native Typescript integration. There are more reasons for this than just technical, obviously, but that's one of the main ones. I think, having been a user of both, the awesome native VSCode integration was a huge factor in Typescript 'beating' Flowtype. It'd be a similar idea for Azure too.