3 ms·
Microsoft (and other large companies, surely) has a huge problem dealing with issues where multiple teams share responsibility. There's no supported way to use
by mastax 6y ago
Microsoft (and other large companies, surely) has a huge problem dealing with issues where multiple teams share responsibility. There's no supported way to use DirectX (or Direct 2D or DXGI or ...) from .NET. They know there's relatively large demand for it, but the .NET team says "I'll forward that to the DirectX team" and the DirectX team says "we just do C++ over here." The default response to cross-cutting concerns should be that both teams take responsibility but right now neither team will take responsibility. Another corollary to Conway's Law.
- JamesBarney 6y agoI've always heard the phrase, "if two people are responsible, no one is responsible".
- Razengan 6y ago> There's no supported way to use DirectX (or Direct 2D or DXGI or ...) from .NET Wow, they’re still treating .NET as a second class citizen?? That’s one of the biggest reasons I jumped off the MS boat. At least Apple is going all-in on Swift and actually using their latest tech in core parts of their OSes (unlike MS and things like WPF etc.)
- tinus_hn 6y agoWell you can’t expect Microsoft to rewrite all their software in the framework of the week, right?
- silon42 6y agoThat would be stupid. /s? They could have an official .NET wrapper for DirectX, but then it's not "direct" :) anymore. Of course then the next question is whether it works on Mac/Linux/... in dotnet.core which is in conflict with their inner lockin tendency