topshell

ons without basically writing a full-blown custom parser - can sometimes be difficult to distribute a minimal-dependency release to remote machines or other users Functional languages are awesome for many of these things, but can be awkward when dealing with the side-effects that we normally want when dealing with scripting tasks. So far, what I gather from your readme/wiki is that TopShell is: a) A functional language seemingly inspired by ML, Haskell, et al. b) A reactive development environment for the language, à la Jupyter I love the code examples in the readme; I think this is something most people want to see but a lot of projects overlook. However, I think the readme is a bit barren on the philosophical front. You have a great wiki page [0] for that - I think it could be condensed and integrated into your readme so new visitors have a good idea of your vision. As someone who would consider using TopShell, my concerns are: - I can't find documentation on how I can use my own editor/environment if I want, rather than the web interface (which is nice for its notebook-like experience, but I don't see it fitting into my normal workflow) - I want to continue to integrate with programs which adhere to the unix philosophy; how does TopShell fit into this? - How dedicated are you to the development/maintenance of the project? - Do you forsee growing a community of contributors (and if so, how?), or do you want to keep this as a personal pet project? - Do you think the project will be alive in 1, 3, 5 years? [0]: https://github.com/topshell-language/topshell/wiki/TopShell:...