[rekado]

GNU Guix. It uses code staging a lot, which works best in a language in which you can trivially pass around code as data.

It also demonstrates that Scheme is flexible enough to easily implement features that the language designers did not, such as monads and laziness. While both can be done in almost any language, I think that Scheme's macros allow for exceptionally seamless implementations.

[Bromskloss]

> code staging

I'm trying to look up what this means. Do you have a link?

[rekado]

In Guix not only package definitions are written in Scheme, but also build phases. These build phases are evaluated at a different time in the context of the build daemon. This means that there are two major strata, both of which are written in Scheme. Expressions that are evaluated in the build context look no different than other expressions.

That's not the only instance of "staged" execution. Guix introduces G-expressions, a quoted expression in a build context where unquoted package values are replaced with absolute directory names that are not known until execution time.

Quoting and unquoting code and dealing with different strata of evaluation come natural in Scheme.

Another simpler example of staged execution might be the remote code execution feature of Guile-SSH.

You may also like to read about multitier programming in Hop: http://queue.acm.org/detail.cfm?id=2330089

[kazinator]

"Code staging" is a phrase that is used around people who are allergic to the word "macro", because they associate it with #define, or "Excel macro".