4 ms·
How was it the right decision? Silverlight was cross-platform, then they made a Windows-specific fork which is WinRT XAML/WinUI (most people don't realize this
by contextfree 7y ago
How was it the right decision? Silverlight was cross-platform, then they made a Windows-specific fork which is WinRT XAML/WinUI (most people don't realize this but this stack originated as a repurposing of the Silverlight codebase directly, it wasn't a rewrite), now they are apparently hoping to make it cross platform again (see e.g., https://www.theregister.co.uk/2019/11/20/winui_winrt_windows_api_webassembly/ https://www.theregister.co.uk/2019/11/20/winui_winrt_windows... )
It seems like they could have taken a less roundabout route to get there.
- NicoJuicy 7y agoWinUI is based on .net core. Silverlight on .net framework. At the time, it was not easy to port WPF to core ( mostly because of System.Drawing), they did it now and it's a new framework.
- contextfree 7y agoSilverlight wasn't built on the full .NET Framework CLR, it was built on CoreCLR which was the direct ancestor of today's .NET Core. From https://docs.microsoft.com/enus/dotnet/standard/glossary https://docs.microsoft.com/enus/dotnet/standard/glossary : "Originally, CoreCLR was the runtime of Silverlight and was designed to run on multiple platforms, specifically Windows and OS X. CoreCLR is now part of .NET Core and represents a simplified version of the CLR. It's still a cross-platform runtime, now including support for many Linux distributions. CoreCLR is also a virtual machine with JIT and code execution capabilities."