kobold VS Umpire

https://github.com/maciejhirsz/kobold is kind of like svelte in rust. It is pretty new (announced this month?). The difficulty with that approach is the integration with rust analyzer and rustfmt. Macros don't work with formatting and rust analyzer can have difficulty with them. Frameworks like Leptos and Dioxus keep the macros isolated to the view, but for a svelte like framework you need the whole file to be a macro.

That does create a bunch of little .js files unfortunately, but they are quite easy to bundle for production. Ideally trunk should be doing that itself (as per closing remarks in the post).

* https://github.com/joshhansen/Umpire

The reason for this is that I'd like to use an RAII pattern to control player turns in Umpire. When the struct is initialized, it starts the player's turn, and when the struct is dropped, it ends the player's turn.

Wound up with some time so I figured I'd port my Umpire military strategy game to a client-server architecture so people can play it online. This will give me some experience with Tokio, tarpc, and async Rust generally, since I'm eyeing a possible Rust dev gig in my future.

I've done a little bit of Rust development on Windows and had a good experience. I ported my (still unfinished) Umpire game to Windows pretty easily. I had to rename some files that had colons in the filename which Windows didn't like. The actual hard part was the terminal library, but switching to crossterm was pretty straightforward. All in all it was pretty painless.