1. 6
  1.  

  2. 5

    I have been in touch with JRB recently and have been trying to get the CVS history for Goo to put on GitHub to preserve the history.

    I have also been working to recover the old wiki contents.

    I am just doing this for archival purposes, not to try to revive the language. Open Dylan is enough work for me as it is. :)

    1. 2

      The important thing missing from this page is why Jonathan Bachrach and the other people whose names are smaller lost interest in their creation in 2005.

      1. 1

        Don’t know about the other 4, but JRB is at Berkeley now and working on Chisel, which is probably taking up most of his time.

      2. 1

        Programming language archeology, anyone? (The linked page seems to be about a decade old and has broken links to the mailing list and news.)

        Seriously, though, does any maintained language occupy this space? Is there “a simpler, more dynamic, lisp-syntaxed Dylan … and an object-oriented Scheme” that “offer[s] the best of both scripting and delivery languages”, with dynamic compilation and type inference (and no VM)?

        1. 5

          Open Dylan is actively maintained and developed. We are working with someone (from the old Dylan and SK8 teams at Apple) on an experimental s-expression reader for Open Dylan. We aren’t sure yet where that will go or on what timeline.

          As for an OO-scheme, there was rscheme which was interesting and inspired some by Dylan, IIRC.

          Creating such a system from scratch is a huge amount of work though, which is why I had chosen to help revive Dylan and push it further.