ChezScheme VS racket-markdown-blog

The main line of Chez Scheme is here:

https://github.com/cisco/ChezScheme

There is more work to be done before release 10.0.

What is yakihonne? Another blogging platform? Rather confusing to use.

Anyway, would have been nice for the article to link to Chez Scheme project's page, which seems to be this one:

https://github.com/cisco/ChezScheme

Also not clear why should folks use Chez? The article barely covered the why or what successful apps have been written in Chez.

Who will convince Kent to come back and make r6.1rs? https://github.com/cisco/ChezScheme/issues/574

If you want a large language, isn't it a better idea to build it on top of something the makes better guarantees for the user? I prefer my program to not continue executing after reaching an erroneous state.

So far as I know Chez is not a variation on Guile, it's a scheme implementation similar to Guile, and so far that I can see Guile is more active, with more community and more package ecosystem , and looks like Chez is/was a cisco project, not sure how is the development process there, but Guile looks like more active in terms of commits https://git.savannah.gnu.org/cgit/guile.git, the last one in "main" is 3 weeks ago vs may 23 https://github.com/cisco/ChezScheme/commits/main.

The link doesn't work for me but to answer the title, I found it interesting to learn that Chez Scheme (often regarded as the Scheme implementation which produces the fastest programs) is developed by Cisco, the company that makes networking hardware

Göran is spot on. I am sad that Marc's proposal on the chez tracker has seemingly died: https://github.com/cisco/ChezScheme/issues/574

Download the exe from here

Many open source project don't allow contributions from people that have worked with similar projects with incompatible licenses. I remember https://github.com/cisco/ChezScheme/pull/376#issuecomment-45... and https://wiki.winehq.org/Developer_FAQ#Copyright_Issues

Huh? Weird, I have written a blog website in what Racket offers, following the documentation you criticize in another comment and got it working. Even the not so easy to understand continuation based side of it came to me after reading it thoroughly. It is quite simple to setup your REST routes and all that.

If you are interested, you may refer to: https://github.com/ZelphirKaltstahl/racket-markdown-blog/tre...

I did never bring it online, as I never rented a server for it, but it definitely functions and I had some local posts, which I did not include in the repository.

Did you never have a software without documentation? I think that would be way worse than having a sort of OK documentation of a bare bones web framework, that is actually understandable, with careful reading.

The Racket mailing list is also very helpful and people there are helpful in my experience. Show them you tried and your attempt at things and they'll probably help you out. My only pain with it is, that they are on Google groups.