4 ms·

For everyone who doesn't work in the MS tech stack, this is pretty standard for the company. I get the sense they're taking a "Manhattan project" approach to g

For everyone who doesn't work in the MS tech stack, this is pretty standard for the company. I get the sense they're taking a "Manhattan project" approach to grabbing cloud share. They find every promising technology they can, and either try to re-implement in their ecosystem or support it. Some of the stuff they're throwing at the wall sticks, and some of it doesn't.

pjmlp 6y ago
True, however for old timers, the recurring politics between WinDev and DevDiv are starting to get tiring.
- kace91 6y ago
  What's that? For non-old timers :P
  - asdfman123 6y ago
    More to the point, how many divs could a WinDev dev if a WinDev could dev divs?
  - pjmlp 6y ago
    WindDev owns Windows and C++ development related tooling, meanwhile DevTools is responsible for .NET and Visual Studio. Since the introduction of .NET, when you seen Microsoft going all .NET, or having a cycle talking about why native is good and .NET should only be for LOB, it reveals which division is winning the political shots. Some examples, Longhorn's failure, only to redo many of its ideas with COM in Vista, which ended up in WinRT. WinRT/UWP looks suspiciously similar to ideas that gave birth to .NET, before it was decided to create a managed runtime instead (Ext-VOS) project. Midori also proved it's capabilities by running part of Bing for a while, but it wasn't enough. Joe Duffy has a remark on its Rustconf keynote, that even when proven wrong and given the opportunity to test drive Midori, the Windows team wasn't willing to change their mind. Then you have them killing C++/CX in name of ISO compatibility, although UWP is anyway Windows only. So now DevDiv has to wait for the day ISO C++ supports the reflection and metaclasses, so that they can replicate the C++/CX tooling experience introduced in 2012.
sdenton4 6y ago
I seen to remember the Manhattan project being a bit more single minded in it's focus. :)
- wrs 6y ago
  They took multiple parallel approaches to bomb configuration and fissile element enrichment (at great expense) because they didn’t know what was going to work. Sort of like what’s happening with vaccines right now.

pjmlp 6y ago

True, however for old timers, the recurring politics between WinDev and DevDiv are starting to get tiring.

kace91 6y ago
What's that? For non-old timers :P
- asdfman123 6y ago
  More to the point, how many divs could a WinDev dev if a WinDev could dev divs?
- pjmlp 6y ago
  WindDev owns Windows and C++ development related tooling, meanwhile DevTools is responsible for .NET and Visual Studio. Since the introduction of .NET, when you seen Microsoft going all .NET, or having a cycle talking about why native is good and .NET should only be for LOB, it reveals which division is winning the political shots. Some examples, Longhorn's failure, only to redo many of its ideas with COM in Vista, which ended up in WinRT. WinRT/UWP looks suspiciously similar to ideas that gave birth to .NET, before it was decided to create a managed runtime instead (Ext-VOS) project. Midori also proved it's capabilities by running part of Bing for a while, but it wasn't enough. Joe Duffy has a remark on its Rustconf keynote, that even when proven wrong and given the opportunity to test drive Midori, the Windows team wasn't willing to change their mind. Then you have them killing C++/CX in name of ISO compatibility, although UWP is anyway Windows only. So now DevDiv has to wait for the day ISO C++ supports the reflection and metaclasses, so that they can replicate the C++/CX tooling experience introduced in 2012.

sdenton4 6y ago

I seen to remember the Manhattan project being a bit more single minded in it's focus. :)

wrs 6y ago
They took multiple parallel approaches to bomb configuration and fissile element enrichment (at great expense) because they didn’t know what was going to work. Sort of like what’s happening with vaccines right now.