alchemy VS winsafe

1) This was started years ago back when SwiftUI had, frankly, a mountain of problems. I originally did the seeds of this work when building out Alchemy, a React clone for cross-platform apps in Rust. I sunset that project due to personal issues in my life at the time (relative dying) which had destroyed my motivation/time. I ultimately chose to extract the codebase and make cacao since it filled a necessary niche in the ecosystem.

Ah, yes - though I think we're still ultimately after the same thing. Cacao, while it tries to unify AppKit/UIKit APIs, more or less treats UIKit APIs as the "blessed" ones. A good example is the ListView component, which pretty much limits an NSTableView to the style and such that you'd find over on UITableView. cacao just has more working AppKit code due to it being originally the basis for alchemy.

Oh cool! Glad to hear it - I experimented with VDOM stuff long ago back in alchemy and considered returning to it at some point, but if someone else does it... well, it'd be hella cool.

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: