News for hackers. Stuff that matters.
Re:Zero-click, wormable, cross-platform remote code executio... by mastax on Monday December 07, 2020 @07:03PM (#25339542)
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.
Re:Zero-click, wormable, cross-platform remote code executio... by JamesBarney on Monday December 07, 2020 @08:14PM (#25340286)
I've always heard the phrase, "if two people are responsible, no one is responsible".
Re:Zero-click, wormable, cross-platform remote code executio... by Razengan on Monday December 07, 2020 @09:40PM (#25341009)
> 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.)

Re:Zero-click, wormable, cross-platform remote code executio... by tinus_hn on Wednesday December 09, 2020 @06:19AM (#25357482)
Well you can’t expect Microsoft to rewrite all their software in the framework of the week, right?
Re:Zero-click, wormable, cross-platform remote code executio... by silon42 on Wednesday December 09, 2020 @07:46AM (#25357927)
That 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