json-tail VS react-native-windows

For one, you have a better control on the GUI. Don't get me wrong, I actually ship the tools I build also as little servers (example: https://github.com/egeozcan/json-tail) but there are also disadvantages to this.

I've made a half-baked newline separated JSON tailer for my small use case: https://github.com/egeozcan/json-tail

it's super bare-bones, and the golang side of things could have been much better, but it kind of works.

Microsoft is using React Native for Windows [0] for their Office applications [1]. As a fan of RN this would be the first avenue I’d explore if I had to develop something for Windows.

[0] https://microsoft.github.io/react-native-windows/

There's also MAUI (.NET) and React Native desktop.

Sometimes yeah they can become a real pain in the a$$. With RN you can make good looking and dynamic layouts with minimum effort. On the other hand when trying to implement logic my main and continuous issues I am facing is with the async parts . Apart from I am all in for RN . I am going to give it a try for a windows app with https://microsoft.github.io/react-native-windows .And if it works fine (which means you get your self away from C#) it will be a really powerful tool for me .

You can read more about it here: https://microsoft.github.io/react-native-windows/

at Microsoft, it's used a lot for brownfield scenarios, similar to react-native-windows: https://github.com/microsoft/react-native-windows

you sound more like a zealot than someone trying to make a point. you can deploy to desktop with react native and have been able to for years now, courtesy of Microsoft: https://microsoft.github.io/react-native-windows/