2 ms·

What a waste of time... It's like the "smug lisp weenies" of ages past somehow slipped into the modern era. Janet is a nice embeddable Lisp (that is: it belong

What a waste of time... It's like the "smug lisp weenies" of ages past somehow slipped into the modern era. Janet is a nice embeddable Lisp (that is: it belongs to the Lisp family of languages). I've been meaning to play with it, but concluded that the lack of (robust) stdlib would make it hard to use for standalone applications. Was it a problem for you in practice, or is the small stdlib enough for CLI apps?

frompdx 6y ago
I do wish there was an http client/server component in the stdlib. That's probably my biggest gripe at the moment. I think things are evolving in the right direction though. Recent updates have added an event loop module and have improved the net module. I can see a future where Janet becomes very useful for network programming. I think http in stdlib plus some growth in the third party package ecosystem will make Janet more viable. I mostly stick to using it as a gluing tool for shell scripts for now. So for my purposes it was fine for CLI apps assuming you are gluing together other cli apps. I could have avoided some gluing if Janet had it's own http client. I spent a while trying to dig into some of the packages and to be honest they just aren't there yet. I really wanted to experiment with building a desktop GUI in Janet but I found that it was too much effort to get started. Cljfx (clojure) and racket/gui both work out of the box with minimal effort.
- lenkite 6y ago
  "I mostly stick to using it as a gluing tool for shell scripts for now." You might like https://github.com/babashka/babashka https://github.com/babashka/babashka then.
yumaikas 6y ago
I've been using Janet quite a bit for small CLI apps. The stdlib is quite enough for basic CLI apps, especially when you use PEGs. Janet's event loop also makes it very handy for issuing a lot of subprocess calls. Janet has basic HTTP servers and clients, and there is an effort to shore it up there.

frompdx 6y ago

I do wish there was an http client/server component in the stdlib. That's probably my biggest gripe at the moment. I think things are evolving in the right direction though. Recent updates have added an event loop module and have improved the net module. I can see a future where Janet becomes very useful for network programming. I think http in stdlib plus some growth in the third party package ecosystem will make Janet more viable. I mostly stick to using it as a gluing tool for shell scripts for now. So for my purposes it was fine for CLI apps assuming you are gluing together other cli apps. I could have avoided some gluing if Janet had it's own http client. I spent a while trying to dig into some of the packages and to be honest they just aren't there yet. I really wanted to experiment with building a desktop GUI in Janet but I found that it was too much effort to get started. Cljfx (clojure) and racket/gui both work out of the box with minimal effort.

lenkite 6y ago
"I mostly stick to using it as a gluing tool for shell scripts for now." You might like https://github.com/babashka/babashka https://github.com/babashka/babashka then.

yumaikas 6y ago

I've been using Janet quite a bit for small CLI apps. The stdlib is quite enough for basic CLI apps, especially when you use PEGs. Janet's event loop also makes it very handy for issuing a lot of subprocess calls. Janet has basic HTTP servers and clients, and there is an effort to shore it up there.