3 ms·

I currently do this at $DAYJOB with a C++/Qt GUI talking to a Go daemon. It's fine but eventually the busywork in marshalling is a headache, and it doesn't scal

by mappu 2y ago

I currently do this at $DAYJOB with a C++/Qt GUI talking to a Go daemon. It's fine but eventually the busywork in marshalling is a headache, and it doesn't scale well for large amounts of data. I can see some advantage of the therecipe/qt "qtbox" idea. Even though the same marshalling is present, you get to write everything still in one language, the cross-language part is hidden from you. In either case, it's great that MIQT now lets you avoid this, and write everything in Go with no IPC marshalling at all.

chipdart 2y ago
> Even though the same marshalling is present, you get to write everything still in one language, the cross-language part is hidden from you. The hard part of writing a desktop application is the GUI code, and how to implement user flows and how to manage the application state. Adopting a highly non-standard technology to handle the hard part and on top of that adopt an ad-hoc IPC solution to get it to work sounds like putting all the project risks in all the wrong places.