> Last year, I was working on an article called 'An Opinionated Guide to Scheme
> Implementations' in order to address the newbie question of 'What implementation
> should I start with?' Amirouche asked me to share the draft here, but I
> completely forgot about the whole thing.
>
> Today he helpfully reminded me again and I feel obliged to share the half-baked
> draft. It's fairly short and in plaintext but I decided not to clutter your
> mailboxes so I'm uploading it to a pastebin service.
>
> https://clbin.com/ztikI

Looks great! You are very good at organizing information and presenting
it in an easy-to-understand way.

There's a lot of implementation data that aspires to be machine-readable
at <https://github.com/schemedoc/implementation-metadata>. We could
think about adding some parts there and generating a page with mixed
manual and automatic parts somehow.

Amirouche had a prototype of an interactive web page to compare
implementations. I think that would be useful as well. What do you think
- should we have both dynamic and static versions, or should the static
info be integrated into the dynamic page?

> Again, I welcome any feedback. Since I'm not well-versed with the majority of
> Scheme implementations, I'd like to turn this into a collaborative effort and
> draw input from people who actually know how they work. I can share the org file
> if needed.

Much appreciated. IMHO it's fine as it is and we could keep filling in
the missing pieces.

By coincidence, I just created this empty repo yesterday:
<https://github.com/schemedoc/guides>. Feel free to add it there.

We should agree on what markup language (markdown? asciidoc?
restructured text? texinfo? scheme scribe?) to use for Schemedoc stuff.
That's usually a bit of a bikeshed discussion but it's necessary to have
it at some point :) We had a long discussion about it for SRFIs last
year and came to the conclusion that the SRFI submission format should
remain some kind of HTML since we couldn't agree on what else to use.
For Schemedoc we don't have an exising document collection, so we could
pick something that's easier to write than HTML.

Currently there's some GitHub wiki stuff at Schemedoc, but Amirouche
correctly noted that it's getting hard to edit and track the changes.