4 ms·
Here is my cynical view: From what I know they have a history of not using their own tools. They didn't use SourceSafe, but Perforce. Then they made an effort t
by maxxxxx 9y ago
Here is my cynical view: From what I know they have a history of not using their own tools. They didn't use SourceSafe, but Perforce. Then they made an effort to switch to TFS, realized that it sucks and moved on to git.
You can see the same pattern in Windows desktop apps. They didn't use MFC for themselves, didn't use Winforms, used WPF only a little.
- smilekzs 9y agoUWP everywhere now though.
- maxxxxx 9y agoIs that true? Which larger app is written in UWP? Something like Office, Skype or Visual Studio.
- contextfree 9y agoWindows itself is gradually rewriting its shell components in UWP XAML.
- smilekzs 9y agoThere is a watered-down version of Office in UWP. The built-in OneNote is actually this UWP. It uses a different stylus filtering algorithm from the desktop version, which is why I don't use it myself, but rest assured it works just fine.
- deleted 9y ago[deleted]
- WorldMaker 9y agoThe preferred Windows client for Skype has been UWP for a while now (though up until recently it was still often referred to as "Skype Preview").
- eyq1 9y agoIf they didn't use MFC, WinForms and WPF what exactly were they using? Flash?
- maxxxxx 9y agoWin32
- vtbassmatt 9y agoTo be somewhat less cynical, VSS and TFVC were not intended to scale to the size of Windows's codebase, thus they weren't used. And instead of inventing our own thing this time around, we went with (and make contributions back to) the de facto standard. When I was in Xbox, we had a lot of things in TFVC: all the services code, most of the console and Windows apps, and many of the tools. Only the Windows-related bits were in SD.