pagliascii VS whatthefn

I love AsciiDoc and want to use it more. The main problem is, as noted, that it's hard to get this ruby library into whatever platform you want to deploy to. Consequently it's hard to build tooling based on AsciiDoc.

I've had a brief play with trying to implement AsciiDoc in Rust (and others have too, see https://github.com/Veykril/pagliascii). I got bored of trying to figure out what the semantics should be by reading the implementation and decided to wait until the upcoming specification effort at https://asciidoc-wg.eclipse.org/ bears fruit, the Zulip seems a bit more active recently

The Elm model is fine, but it just didn't seem to work well with GTK. I never found much use for message passing - binding or signal callbacks accomplished state changes without much hassle, and fitting into GTK much better. For instance, here's a fairly complex page using subclassing + composite templates via blueprints: https://github.com/JMS55/whatthefn/blob/master/res/blp/profile_setup_page.blp + https://github.com/JMS55/whatthefn/blob/master/src/profile_setup_page.rs.

The code is now open source (GPLv3) https://github.com/JMS55/whatthefn/tree/master/src/perf_data_parser.