New ask Hacker News story: Ask HN: A Lisp with Cargo/NPM like build system?
Ask HN: A Lisp with Cargo/NPM like build system?
2 by nate-sys | 0 comments on Hacker News.
I love lisps, and have played with a bunch of lisps, and schemes. My biggest pain point so far is that almost none of them have a Cargo-like package manager and build system, where packages are installed locally (as in within the project itself), and the project has a predetermined directory structure and entry point. I understand that one of the biggest things most people love about lisp is how much control you have over every single aspect of it and that contributes to most lisps not having a Cargo, per se. The user crafting their own build system __is__ part of the intended experience. But, sometimes I just want to `lisp create my-project` and `cd my-project && lisp repl`. Most importantly, I want to `lisp add a-dependency` without it going to some global directory where conflicts can happen. I am intentionally not mentioning Clojure here because I have been playing with it for a long time and have found that it's not exactly what i'm looking for. Mainly because of how there is more than 1 way of structuring your project (namely leiningen, deps.edn, and friends), and even if you get past that point, i find it difficult to enjoy the command line arguments of these tools (notice how the java creeps into the experience when you `-A:test -Spath`. What I want is a lisp with a compiler/interpreter, and a package manager/build system that makes use of said compiler/interpreter to work on a project using a standardized project structure. Anyway, I want to know if what I'm looking for exists, or if i'm misunderstanding the beauty in the way things are.
2 by nate-sys | 0 comments on Hacker News.
I love lisps, and have played with a bunch of lisps, and schemes. My biggest pain point so far is that almost none of them have a Cargo-like package manager and build system, where packages are installed locally (as in within the project itself), and the project has a predetermined directory structure and entry point. I understand that one of the biggest things most people love about lisp is how much control you have over every single aspect of it and that contributes to most lisps not having a Cargo, per se. The user crafting their own build system __is__ part of the intended experience. But, sometimes I just want to `lisp create my-project` and `cd my-project && lisp repl`. Most importantly, I want to `lisp add a-dependency` without it going to some global directory where conflicts can happen. I am intentionally not mentioning Clojure here because I have been playing with it for a long time and have found that it's not exactly what i'm looking for. Mainly because of how there is more than 1 way of structuring your project (namely leiningen, deps.edn, and friends), and even if you get past that point, i find it difficult to enjoy the command line arguments of these tools (notice how the java creeps into the experience when you `-A:test -Spath`. What I want is a lisp with a compiler/interpreter, and a package manager/build system that makes use of said compiler/interpreter to work on a project using a standardized project structure. Anyway, I want to know if what I'm looking for exists, or if i'm misunderstanding the beauty in the way things are.
Comments
Post a Comment