DDesmaisons

yodon is correct Microsoft has neglected WPF during the last year, and as the same time the javascript commutity was growing fast and hard. So why Neutronium? 1) There is much more javascript/HTML UI components maintened by the community available. Consider for example fantastic library such as D3.js. 2) MVVM is a great pattern but it can be cumbersome to write binding with converters, etc.. With Neutronium, you can use Vue computed for example and reach the result faster. 3) There is much more HTML/CSS designers than WPF designers.

I wrote a .Net assembly analyser/visualizer: https://github.com/NeutroniumCore/CodeDependencyScanner based on Neutronium and D3.js, sincerelly writing a similar software shoudld be an herculean task.

In the case of Neutronium, the framework follows standard MVVM with WPF controls. It can bind same data context as standard wpf component so there is a very smooth learning curve