1. 43
    1. 3

      This is quite neat! Always really neat to see time traveling debugging in action!

    2. 2


    3. 2

      Very cool! I was excited when I read the Spritely Goblins project announcement. It’s an audacious goal and having working artifacts to play with is a serious milestone!

      Looking forward to whatever comes next from these folks!

    4. 2

      It’s always nice to see the progress of the spritely institute. Also, impressive to see it gros that much!

      For the anecdote, i have recently setup a Miniflux instance and hours after I had added the RSS of the spritely website, this was published 😅

    5. 1

      Why, oh why did they have to define a new syntax?

      1. 4

        Goblins is a Scheme library so the code you see is regular Scheme code.

        1. 1

          The whitepaper uses a whitespace-based syntax, which I find absurd.

          1. 2

            I’m partial to s-expressions, too. The Wisp syntax was chosen in an attempt to not scare off people who find s-expressions offputting. Whether it was the right call or not is up for debate. Spritely didn’t invent the syntax, though. Wisp is an alternative Scheme syntax and it is an official SRFI. This paper is an evolving document, so it may be switched back to good ol’ s-expressions if the Wisp experiment doesn’t work out.

            1. 1

              I would definitely love a version of the whitepaper without wisp. If people find s-expression offputting, they’ll use another language with another framework, so I don’t buy the argument. The concepts used by Spritely are complex enough without forcing people to learn another syntax.