I work on http://opendylan.org/ and have been working to revive it for the last couple of years. We've done new releases, improved usability of the compiler and some of the libraries, new website, updated all of the documentation to modern formats, including a couple of books.
We've also been creating a new IDE via a plugin to IntelliJ that is rapidly changing how I go about writing Dylan.
I think it is cool because it is a great substrate for experimenting with some features in programming languages and runtimes, like coroutines and numerics. It is great to start from a working and industrial strength system.
I think it is great to prevent things from being lost to history (and to hopefully have them be useful again). Dylan is a great combination of ideas from Common Lisp, Smalltalk but with a focus on creating native executables and libraries.
I've also got something that I'm building in Dylan that takes advantage of Dylan's strengths, but it is in very early days.
I work on http://opendylan.org/ and have been working to revive it for the last couple of years. We've done new releases, improved usability of the compiler and some of the libraries, new website, updated all of the documentation to modern formats, including a couple of books.
We've also been creating a new IDE via a plugin to IntelliJ that is rapidly changing how I go about writing Dylan.
I think it is cool because it is a great substrate for experimenting with some features in programming languages and runtimes, like coroutines and numerics. It is great to start from a working and industrial strength system.
I think it is great to prevent things from being lost to history (and to hopefully have them be useful again). Dylan is a great combination of ideas from Common Lisp, Smalltalk but with a focus on creating native executables and libraries.
I've also got something that I'm building in Dylan that takes advantage of Dylan's strengths, but it is in very early days.