Possibly unpopular opinion: #wisp is much harder to read than regular #scheme with parenthesis because of all the extra syntax. I think it might be strictly better if the basic whitespace rule was used but parens were simply inserted instead of colon expressions.
In this post Michał Herda explained what Lisp programmers intuitively know.
The parentheses don't bother Lisp programmers as they read code by its indentation and rely on Lisp-aware tools such as editors and IDEs, which match parentheses and properly indent code.
@amoroso This is — in its inverse — part of the argument why I wrote #Wisp: If #Lisp programmers do not pay attention to parentheses then the parentheses are line noise. Ceremony.
Wherever that’s the case, they should be gone.
Because ignoring part of what you see produces mental overhead.
I understood the effect of that overhead when I realized that for the hardest problems it is easier for me to solve them in German (my native language) and then translate them, than solving them in English.
Introducing #defconcommunities ! We’re trying a new kind of content category this year at #defcon31 for creators who don’t fit precisely into slots like Vendors and Villages.
This year at DEF CON you’ll see this new DEF CON Community format in action with creators like #defcongroups , #WISP, and #HDA_DEFCON . Please make some time to visit them and check out their new offerings. As always, thank you for helping us grow and test out new things. See you soon.
If you want to write a game like Dryads Sun yourself, just clone https://hg.sr.ht/~arnebab/dryads-sun — the game is free licensed under AGPL and the tooling under LGPL (so unfree games are possible, though that’s not what I write).