3 ms·

As someone how really like github and really dislikes azure devops - and a corporate direction pushing us from the former to the later - any idea what their end

As someone how really like github and really dislikes azure devops - and a corporate direction pushing us from the former to the later - any idea what their endgame is as these two converge?

lstamour 6y ago
Edit: I misunderstood your comment as about Azure generally and not Azure DevOps specifically. I see Azure DevOps as the “full service” version of GitHub’s slightly more “DIY” approach. DevOps can also be customized and sold by partners, consultants, I think. GitHub if anything, might move more to a “consultant network” approach. I think Microsoft is maintaining two district brands for developers, for the time being. I originally wrote: I think there’s a clear benefit to Microsoft for GitHub to internally use Azure, but I think there’s a clear benefit to Microsoft’s developer community, GitHub and the Microsoft Partner ecosystem for GitHub to support AWS and GCP via open source, AWS Marketplace, Docker and anything else that helps ensure GitHub is useful independent of the rest of Microsoft’s services — GitHub being impartial is more important to Microsoft than the extra market share they might — might — get.
nickspag 6y ago
I also use Azure DevOps for work and am a recently-former MSFT person. From what I've heard from those still there, most of the new development is going towards Github Actions, which is also reflected in their staffing movements. However with GHA running on top of ADO pipeline infrastructure (public info), Microsoft's success with the strategic slow burn as OP called it, and their super-long-term-support reputation, it's probably not in their interest to rush the move. I'd be willing to bet that in a year+ or so the writing on the public wall becomes much clearer. To that extent, we've started planning a migration at my company.
- dathinab 6y ago
  If webhooks become increasingly less useful we will know what thinks are going.
nicoburns 6y ago
The corporate direction could be based on pricing. Azure DevOps (pay per concurrent job) can be a lot cheaper than Github Actions (pay per minute of CI time, with macOS minutes counting as 10 minutes each).
slim 6y ago
the end game is the developer gig economy. you assign a ticket to yourself, write the code while they analyse your behavior to calculate your hourly rate then you get paid
- st-isidore 6y ago
  It might work for low level development tasks (which could very well be most of the software development happening in the world, who knows?), but not for anything more advanced.

As someone how really like github and really dislikes azure devops - and a corporate direction pushing us from the former to the later - any idea what their endgame is as these two converge?

lstamour 6y ago

Edit: I misunderstood your comment as about Azure generally and not Azure DevOps specifically. I see Azure DevOps as the “full service” version of GitHub’s slightly more “DIY” approach. DevOps can also be customized and sold by partners, consultants, I think. GitHub if anything, might move more to a “consultant network” approach. I think Microsoft is maintaining two district brands for developers, for the time being. I originally wrote: I think there’s a clear benefit to Microsoft for GitHub to internally use Azure, but I think there’s a clear benefit to Microsoft’s developer community, GitHub and the Microsoft Partner ecosystem for GitHub to support AWS and GCP via open source, AWS Marketplace, Docker and anything else that helps ensure GitHub is useful independent of the rest of Microsoft’s services — GitHub being impartial is more important to Microsoft than the extra market share they might — might — get.

nickspag 6y ago

I also use Azure DevOps for work and am a recently-former MSFT person. From what I've heard from those still there, most of the new development is going towards Github Actions, which is also reflected in their staffing movements. However with GHA running on top of ADO pipeline infrastructure (public info), Microsoft's success with the strategic slow burn as OP called it, and their super-long-term-support reputation, it's probably not in their interest to rush the move. I'd be willing to bet that in a year+ or so the writing on the public wall becomes much clearer. To that extent, we've started planning a migration at my company.

dathinab 6y ago
If webhooks become increasingly less useful we will know what thinks are going.

nicoburns 6y ago

The corporate direction could be based on pricing. Azure DevOps (pay per concurrent job) can be a lot cheaper than Github Actions (pay per minute of CI time, with macOS minutes counting as 10 minutes each).

slim 6y ago

the end game is the developer gig economy. you assign a ticket to yourself, write the code while they analyse your behavior to calculate your hourly rate then you get paid

st-isidore 6y ago
It might work for low level development tasks (which could very well be most of the software development happening in the world, who knows?), but not for anything more advanced.