3 ms·
One Lisp that doesn't have this con (pun intended!) is Janet. I really like the language, but the documentation is lacking. Otherwise, it's a nice little langua
by behnamoh 1y ago
One Lisp that doesn't have this con (pun intended!) is Janet. I really like the language, but the documentation is lacking. Otherwise, it's a nice little language which compiles to small binaries we can share. It's image-based (!) which is refreshing given how Racket, Clojure, etc. don't support images (at least not that I'm aware of).
- wffurr 1y agoTook me some digging to figure out what you meant by “image”. Seems like a snapshot of the state after loading the file but before executing main.
- kazinator 1y agoIn the mainstream, what adopted the image-based approach is office suite application. What is a document, such as a spreadsheet or wordprocessor (or integrationo of those?) It's a bunch of objects and code saved to disk, revived when you open the document. If you need to explain image-based to people unfamiliar, that's not a bad analogy.
- pbohun 1y agoI recently started using Janet and enjoy it too. I think Rich Hickey got it right when he created a single set of functions to operate on all collections, which fixes most of what's mentioned in the article. Janet does a great job of copying what Clojure got correct. I've found the documentation for Janet to be fairly adequate. What are some parts where the documentation could be better?