Re:Introducing Azure DevOps
by partiallypro on Monday September 10, 2018 @04:46PM
(#17955066)
VSTS naming was a complaint I heard all the way back at Build 2016. Everyone at the Build booth was confused, and even the people manning the booth said the name was confusing. So...it took long enough.
The name made a lot more sense back in the day when the premier client was actually the Visual Studio IDE. But today, most people interact with Azure DevOps with their browser and too many people think "Visual Studio Team Services" is a web-based IDE.
The name change is bittersweet. We've been "Visual Studio <something>" since the first release of our on-premises product, well over a decade ago. But I'm confident about this next phase of Azure DevOps.