4 ms·
They couldn't leave WPF alone to prosper... they had to "improve" it. Then the replacement wasn't good enough and they had to replace that as well. In the proce
by mikece 4y ago
They couldn't leave WPF alone to prosper... they had to "improve" it. Then the replacement wasn't good enough and they had to replace that as well. In the process they pushed product managers to say "Screw it, we'll just build the UI in a browser instead."
If anyone "kills Windows" it will have been Microsoft themselves.
- coldacid 4y agoThe problem with WPF is that it's tied to Windows itself, which isn't of any use in today's cross-platform, .NET 5+ world. (Before you shout, yes I do know about Avalonia. It's nice. But too late.)