Attempt Dioxus port

[l-monninger]

Summary

A small attempt at porting this app to Dioxus, mainly playing around with phenomena related to the runtime as it's been a while since I've used Dioxus.

Presence of this draft and related issues resolves #5.

Takeaways

• Dioxus programmability, via Virtual DOM and state APIs, I think is worth the overhead and opinionation. I think as we look at alternatives for the org standard, the Virtual DOM and state APIs should generally be peers. Templating generally does not seem support our ambitions to be highly programmable and expressible in one language, which itself is motivated by testing, documentation, and readability goals.
• If we want to ship Dioxus, we should plan to develop some kind of IaC, likely for fly.io. I'm mostly off using Terraform or CDKTF at this point. I think we can potentially do a bit better job managing lifecycles in a bespoke API. But, in the least, I would want to bring this a Rust binary.
• It's probably best to pause this here and join productionization efforts under roadline development.

[netlify]

✅ Deploy Preview for amazing-souffle-788c32 canceled.

Name	Link
🔨 Latest commit	ac1aef6
🔍 Latest deploy log	https://app.netlify.com/projects/amazing-souffle-788c32/deploys/689d974178599a00090262ab

[netlify]

✅ Deploy Preview for ramate canceled.

Name	Link
🔨 Latest commit	ac1aef6
🔍 Latest deploy log	https://app.netlify.com/projects/ramate/deploys/689d9741c301fb00078cf335

[l-monninger]

I think #4 should be closed and then re-open as a child of #9. That is, wait for this as the approach should be more maintainable than trying to do this in a JavaScript framework.