Links included below.
I am currently evaluating your C#/XAML product and my initial experiments are encouraging. I am wondering, though, about the consequences in a year or so of C#/XAML -> JS/HTML.
Specifically, my understanding is WebAssembly seems destined to be the future of web programming; currently just C++ compiles but the GC languages (C#, Java, etc.) will follow, running much faster than JavaScript. Then .NET will follow. And maybe even Standard XAML will be ported, though that would be a couple years out if ever.
If this comes to pass, it seems transpiling C#/.NET will be at a severe performance and infrastructure disadvantage. Assuming this is the future, I could see your product still very useful, but eventually replacing your transpiling and pseudo-.NET framework with the "standard" issue from MS/Xamarin/Open-Source combined with your XAML magic.
Have you considered these factors? Would you please help me understand how using your tool would not be signing up for some form of obsolescence?
Thanks,
Tom
https://www.infoworld.com/article/3217704/web-development/whats-new-with-webassembly-portable-code.html
https://hacks.mozilla.org/2017/03/why-webassembly-is-faster-than-asm-js/
https://medium.com/@mbebenita/webassembly-is-30x-faster-than-javascript-c71ea54d2f96
http://www.mono-project.com/news/2017/08/09/hello-webassembly/
https://blog.xamarin.com/glimpse-future-xamarin-forms-3-0/