windigo VS winsafe

I'm writing native Windows apps in Go with Windigo, as a replacement for C++.

I created a couple native Windows apps using Windigo, so it's clearly possible to do the same in Linux, probably with gotk3.

Windigo for low level and native Windows stuff has been extremely useful to me.

I also use Go with VSCode on Windows, and I develop a rather large project. If I change many things at the same time, it may hang, so I have to reload VSCode, but that's it. Nothing serious.

Fyne is just really ugly for me.. I'm trying to learn more about GIO lately (gioui.org) which seems to have a great potential. However you request is very simple: native Windows Gui. And there are few libraries for that: - https://github.com/gonutz/wui - https://github.com/lxn/walk - https://github.com/tadvi/winc - https://github.com/rodrigocfd/windigo

In Windigo there are some specific implementations for x32 and x64 platforms, for example.

I know all that shit because I'm the author of Rust's WinSafe library, which is a safer Rust layer over native Win32, so I had to deal with a lot of shit like this.

[dependencies] winsafe = { git = "https://github.com/rodrigocfd/winsafe", features = ["kernel"] }

Externally, you can write a lot of native Windows stuff in Rust already. Personally, I'm having a lot of fun with WinSafe.

If you had such problems (which I also had in the past), I'm really interested in you opinion about WinSafe, and if it could help you solving them.

If you're after a native Windows application, WinSafe may suit your needs.

As the author of WinSafe, I can say it's tedious sometimes, but it's often very challenging, because you have to translate crazy unsafe behaviors into Rust's ownership model. It's surely hard, but also very rewarding at the end.

As the author of the WinSafe lib, I wholeheartedly agree.

I don't know how rare this is (or how rare it should be), but this issue warned me about this potential problem, and I had to make a huge refactoring to treat the possibility. I had to rethink many aspects of all handle implementations. It was hard work, but in the end it was worth it.

WinSafe says hello.

WinSafe, for example (which attemps to be a safe layer over the Windows API), provides lots of RAII automations. A fine example is the BeginPaint function: