@jonn I have transitioned quite fast but I was hygely surprised when it went absent from my system since I treated it almost as part of POSIX, anyway I see some aux tooling scripts that depends on it all the time
@chodzikman I knew I shouldn't. But I spent so much time with ifconfig, route and, later, wpa-supplicant as a kid and teenager, I kinda feel as scared of learning new tools as I was of those.
@jonn yeah same here with Ubuntu 5.10 or something but with Arch (btw) I learned not to stay behind to avoid awful fate 🥵
@chodzikman haha, with arch I learned that arch sucks. let's be real, the only reason we were using it was because of AUR. With nix, you don't need AUR. :)
@jonn not yet in my nix chapter - I feel like I became immune for the plot twists after ~10yrs of using Arch, not being aware of it, but recently I advised to use it to few of my friends and it went awkward
... I guess I need to be in a situation where I create a reference setup in a lazy greenfield project to hop into the nixos hypetrain...
@chodzikman oh no, no #NixOS for me. They still can't figure out whether or not to have #flake functionality on by default or not. Even in absence of any good arguments for not including them. It's just a mess and "steering" feels like a mess too.
Honestly, if someone will make a typed #nix that's backwards compatible with nixpkgs and flakes, I'm gonna be a happy customer of *that*.
That said, I'm only talking about #nix itself and #nixpkgs. Specifically, nix with flakes.
@jonn @chodzikman I think Nickel is supposed to be that.
@6d03 @jonn @chodzikman I'm happy to learn that people are considering moving away from the language, but I don't feel going to another esolang will help with adoption.
@alper @6d03 @chodzikman there there
@jonn @6d03 @chodzikman I mean there’s no story for getting a critical mass of programmers on either nixlang or nickel, is there?
@alper @6d03 @chodzikman ah snap, it's the wrong thread (my threads don't load on iPhone app, so I thought you're answering another thread and call haskell and lean esolangs).
Yeah, nickel is doomed, we need to compile normal languages to nix. But then again... The source language should be lazy, which really just leaves haskell as the source language.
@alper yeah, it's not like Eelco wanted to make a new language, he just needed a small language with lazy evaluation strategy.
@jonn Ugh, I see. Disappointing that there is so little choice here.
Then I also understand why they created their own weird mesh of bash and Haskell. It’s not that bad, just the syntax is not very enticing.