nimble

Fwiw, the name clashes with Nim's package manager nimble: https://github.com/nim-lang/nimble

I was using Nim for some of last years Advent of Code problems. I was mostly liking the syntax. Was a bit bother by the standard library have a snake case and camel case reference for each function (if I'm remember that correctly). At the time nimble also required me to have NPM to install the the Nim package manager, Nimble. This was not ideal, but looking at [the nimble project install docs](https://github.com/nim-lang/nimble#installation) it seems like it is now package with the language. Might try dusting it off for some AoC puzzles this year :)

`nimble` is the package manager for the programming language `nim` [1]. From [2], we can see that `nimble scss` simply generates the CSS files for the frontend. The benefit of OSS is you can answer these questions yourself with a bit of poking around! IMO this is a fairly standard installation process, maybe the fact that it's using Nim instead of a more mainstream language makes it look more daunting than it is. The only out-of-the-ordinary thing here, IMO, is `nimble build` instead of `make build`. [1]: https://github.com/nim-lang/nimble [2]: https://github.com/zedeus/nitter/blob/master/nitter.nimble

Something I'm excited about: v1.6.2 integrates support for (not yet released) Nimble[1] v0.14, which will introduce project lockfiles. I've had terrible experiences with lockfiles in JS land, but they are sorely needed for Nim projects as (fingers crossed) they'll allow for reproducible builds without having to resort to the nimbus-build-system[2]. The latter isn't completely horrible — a lot of much appreciated hard work has gone into it, and it's been a real workhorse — but some days it feels like a big ball and chain. I'll be much happier when I can cruise along with choosenim[3] and lockfiles and not have to worry about Makefile + submodules shenanigans. [1] https://github.com/nim-lang/nimble#readme [2] https://github.com/status-im/nimbus-build-system#readme [3] https://github.com/dom96/choosenim#readme

For a while now I've been looking at using Nim, and this weekend I did my first project with it: a tool for creating binary wrappers. In Nixpkgs we often create wrappers, but those have thus far been shell scripts causing trouble at times on e.g. OSX. https://github.com/NixOS/nixpkgs/pull/95569 I found it easy to get up to speed and do something useful with it. The language is also in my opinion very readable. The documentation could use some more (larger) examples though. For this wrappers tool I needed a front-end for which I wanted to create an interface with argparse. Unfortunately the standard library lacks an implementation, and third-party packages did not deliver what I needed. In the end I wrote that part in Python still. The biggest issue I currently find is the lack of a lock file format for its package manager. It's being deve

This is really cool. I'm excited to integrate it with Nim's package manager Nimble [1]. It will be a little strange though, since Nimble packages just need to be tagged in git and then you've got a release. It doesn't seem that GitHub implemented it this way. 1 - https://github.com/nim-lang/nimble

> However, the ecosystems are not at all comparable. Really? https://github.com/VPashkov/awesome-nim You can install Nim packages easily with nimble. https://github.com/nim-lang/nimble

> as someone doing precisely this kind of engineering for almost three decades, I can assure you that this is not the case Same here. > Unless one is an operating system vendor (like Joyent, redhat, SuSE, Debian, Canonical, CentOS, ...) third party and unbundled applications must never be installed into /usr That's what I wrote: "native package managers should install binaries in /usr/[s]bin and libraries under /usr" "native" as in: provided by the distribution. Not third party. https://github.com/nim-lang/nimble/issues/80 is about using /opt/nimble and you wrote "If you implement that, you instantaneously take away the ability to deploy applications through OS's automated deployment", hence the confusion.

oh, guess I shouldn't implement that[1] then :) To be honest, now that I'm thinking about it again, I think you're totally right. 1 - https://github.com/nim-lang/nimble/issues/80

Apologies. I meant production ready package manager. The one I'm aware about is in beta. https://github.com/nim-lang/nimble

Hehe, good idea, but that clashes with the name of our package manager: https://github.com/nim-lang/nimble :)

> Nimble file naming [0]. It must end in '.nimble', and must have at least character in front of that suffix, but the prefix doesn't actually matter. It does now. The new NimScript .nimble format[1] uses this prefix to determine the name of the package. 1 - https://github.com/nim-lang/nimble#the-new-nimscript-format

> Lots of small little quirks that weren't greatly documented. > For instance? Nimble file naming [0]. It must end in '.nimble', and must have at least character in front of that suffix, but the prefix doesn't actually matter. I'm not convinced on the maintainability argument. Many, many projects have a coding style guide. LISPs require one too. Once you have one, maintaining the code becomes as difficult as any other language. I've encountered unmaintainable Python code [1], and insanely well documented Scheme code [2]. I'm not sure the language has much to do with it, apart from supporting a wide range of paradigms and patterns. I'm not sure black-boxing through use of a sophisticated framework is any better than the way you work in more flexible languages. Here's my take: * Nim is great. The use of the 'auto' keyword let me be producti

Didn't really see a ton of substance in that, it seemed to mainly add up to a long-winded explanation of printing out a text file using two different languages in convoluted ways. Here is my much shorter version of basically the same thing with a different language: Nim for Node.js Programmers I love Node.js programming, especially because of the massive ecosystem of modules available, but Nim has some advantages in many cases. Here are three: it uses very little memory, creates code that is very fast, and interfaces extremely easily with C and C++. ### Node.js How to set up Node Since you are a Node programmer, you already have it set up. const fs = require('fs'); fs.readFile('hello.txt', 'utf8', (err, data) => { if (err) { console.error('Problem reading file:', err); } else { console.log(data);