Garn, a TypeScript-based Nix front end
1–10 of 23 posts
Re: Garn, a TypeScript-based Nix front end
#2Re: Garn, a TypeScript-based Nix front end
#3I'm interested to know if this finally will help me to enter nix world, I tried so many times but failed.
Yeah, that's definitely the intention. If you end up trying it out, I'd love to hear how it went!
Re: Garn, a TypeScript-based Nix front end
#4Re: Garn, a TypeScript-based Nix front end
#5I'm interested to know if this finally will help me to enter nix world, I tried so many times but failed.
(One of the `garn` developers here.) Yeah, that's definitely the intention. If you end up trying it out, I'd love to hear how it went!
But maybe that would create too much overhead..
Re: Garn, a TypeScript-based Nix front end
#6Earlier quoted context omitted.
(One of the `garn` developers here.) Yeah, that's definitely the intention. If you end up trying it out, I'd love to hear how it went!
Have you thought about a GUI layer on top of that, named uberhaupt? But maybe that would create too much overhead..
Re: Garn, a TypeScript-based Nix front end
#7What’s the rationale for the heavy use of tagged template literals in the API? From the outside, it seems like an esoteric choice that makes ergonomics slightly worse, less approachable, and less idiomatic. This seems to fly directly in the face of the goals of this project.
All that said, I could be convinced that the API choice isn’t a mistake.
At any rate, I’m excited to see where this project goes.
Re: Garn, a TypeScript-based Nix front end
#8I am thrilled to hear that this effort exists. What’s the rationale for the heavy use of tagged template literals in the API? From the outside, it seems like an esoteric choice that makes ergonomics slightly worse, less approachable, and less idiomatic. This seems to fly directly in the face of the goals of this project. All that said, I could be convinced that the API choice isn’t a mistake. At any rate, I’m excited…
Re: Garn, a TypeScript-based Nix front end
#9I am thrilled to hear that this effort exists. What’s the rationale for the heavy use of tagged template literals in the API? From the outside, it seems like an esoteric choice that makes ergonomics slightly worse, less approachable, and less idiomatic. This seems to fly directly in the face of the goals of this project. All that said, I could be convinced that the API choice isn’t a mistake. At any rate, I’m excited…
It’s to allow interpolation of packages and environments. But in practice we don’t use it that often, so we were thinking of switching the main function to using just a second string argument. (In other words, I agree.)