ChezScheme VS ink

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/thesephist/ink is a good example. You can hear its author in metamuse podcast 42 https://podcasts.apple.com/ru/podcast/metamuse/id1504506097

Go seemed to work quite well for Ink (https://github.com/thesephist/ink) and I liked that I didn't need to worry about picking the right dependancies (e.g. like with Rust) because Go's standard library covers all the use-cases of building a general purpose language.

Ink programming language\ (14 comments)

For someone who care the implementation than the high-level design: It's written in go, interpreter-based, and pretty small [1].

Although the author seems to be a well-studied PL lover, you don't have to be like this to create a small language. It's fun experience and there are books for non-experts like [3].

- [1] https://github.com/thesephist/ink/tree/master/pkg/ink

- [2] https://thesephist.com/posts/pl/

- [3] https://interpreterbook.com/