@dom96 But picknim was much cuter. Is Nintendo now so legally trigger happy that they will sue over name similarity to Pickmin?
@Libman Once choosenim is ready for prime time, maybe we don't need to rely on OS specific packages. If choosenim becomes to Nim what rustup is to Rust or what stack is to Haskell and if choosenim will not depend on Nim itself being installed, maybe the best default installation method would be to have an OS installer package for choosenim and let choosenim take it from there. Reasons: * If your'e as small as Nim still is, having OS specific packages updated regularly can be hard, even if you nag maintainers. A tool like choosenim should have a much lower update frequency than Nim and maybe can even update itself. * OS package managers generally do global installs and the acceptance of rustup/stack shows that most devs want something more flexible, especially as long as a new languge is somewhat in flux. The only unavoidable use case for a global install I can think of is Nim scripting (apart from choosenim possibly depending on Nim in some other way). * Linux package management is moving in the direction of cross-platform models based on things like AppArmor and systemd (e.g. Ubuntu snap). This might be kind of ok for apps, but IMHO not for more complex cases like a prog language toolchain. If this catches on, we better depend on something like choosenim.
