ChezScheme VS web-tutorial

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

https://github.com/soegaard/web-tutorial/blob/master/listit3/control.rkt#L135

Jesse Alama here. If you bought a book from me but are unsatisfied, I'm happy to refund you. If you found my stuff unhelpful, let me know what's missing and I can try to include a discussion of that in the next edition. Just write me offline. Or write to the group, or visit us (or me) in the Racket Slack.

I wrote my stuff to help people get into web development with Racket. I love web devel, and Racket, too. You and I have a lot in common: I found the official docs puzzling, so I worked out my own approach to them and made _Server: Racket_. It should go without saying that that's the origin story of just about every paid book out there on applications of programming language X to domain Y. That's not even a criticism of the Racket docs. Plenty of tools/languages also have good docs, and there are lots of books, too. How many Django books (or even courses) are out there?

There are also some great web programming tutorials out there for Racket, too. I recommend this one, by Racket star Jens Axel Søgaard: https://github.com/soegaard/web-tutorial .

I hope you'd give Racket a chance. Since you're talking about it, it sounds like you're dipping your toes in the waters. I'm pretty sure you'll find them quite welcoming. That said, all this negativity is pretty off-putting.