3 ms·
Exactly, i have no idea what happened, why all these frameworks were treated like that. XAML, Flex, and many others. Well Google tried to make a bridge with CEF
by mlsarecmg 10y ago
Exactly, i have no idea what happened, why all these frameworks were treated like that. XAML, Flex, and many others. Well Google tried to make a bridge with CEF (Chromium embedded framework) which had .net bindings but it was quite slow last time i tried. Not a real UI framework of course.
I come from a .net/C++/C# background, too, and i disliked Javascript strongly back then when it was still a rumor that WPF would go down. But it's in a very different shape today and i mean the language itself, not just the community aspect of it. I write code in it that i would struggle with in C#. Javascript being very close to its JSON backbone and having special operators to mutate variations of it, i miss that in C#. Or dead simple async, caching, networking, it all feels very close to the core. Now where they implement atomics and shared buffers, there are very few things i would miss.
The type system has also gotten better, especially with Facebooks Flow, which is very sound and can detect deeply nested cases.