Hacker News Reader

I really like this approach, particularly since it allows a clean separation between the responsibilities of designing the UI and writing the back-end code. The UI designer can still wire up events and design them in Qt Creator (maybe using placeholder events?) but then the .NET dev can write the back-end stuff for it.

Exactly.

The tech-stack perfectly slices responsibilities. That is what really motivated me to do it. Seemed like peanut butter and jelly.

Also, performance. Anything beats electron.

Very nice. I have used both WPF/XAML and QML and definitely find QML's model much more intuitive (anchors make things so much easier). Looking forward to trying it out!

Awesome. Starred!

that's great! you should consider sharing this on the Qt mailing list.