3 ms·
I've written a bit of Scheme in production. What I've found is that S-Expressions are unambiguous, and easy to learn, but Scheme doesn't railroad you with them.
by shakna 9y ago
I've written a bit of Scheme in production. What I've found is that S-Expressions are unambiguous, and easy to learn, but Scheme doesn't railroad you with them. There's other options as well.
A more recent project used the traditional syntax for macro-files. We seperated those out, a bit like C-header files, because it was easier for a macro-traceback library we created.
Most of the main files were in Wisp, which decreased the learning time for our Pythonistas.
Finally our hot-paths tended to be Cish. That is, they were compiled C at release, but Scheme with a C reader macro at development. (Based around Racket's c-lang).
Of all of these, I prefer Scheme's traditional syntax, maybe with the curly infix extension for dealing with OO when I have to (like interfacing with Java).
I know a lot that swear by Wisp, however.
Finally, a lot of people like Cs syntax.
I think syntax is something that people look for familiarity in, just as much as useability.
Reducing cognitive load is important, and background is highly influential.
For me, I've yet to see something beat S-Expressions. But I don't expect that can be true of everyone.
I wish pluggable syntax appeared in a wider range of languages.