My experience with NixOS

Post by rtu8lu » Wed, Apr 15, 2020, 8:37 PM UTC

therein wrote: post #47

mbakke wrote: post #43

Earlier quoted context omitted.

One common beginner mistake is attempting to modify files in the immutable store directly. Don't do that. The system is read only for a reason. Also make sure you allocate enough space on your root partition so you don't have to run garbage collection all the time.

I made the switch from Arch about a week ago. So far, great experience. I love the fact that my system state is reproducible and if I use version control on my dotfiles, I basically have a full backup of the look and feel of my workstation. VFIO with GPU passthrough works flawlessly. Setting up FDE with LUKS during and after the install was a breeze as well. Really enjoyed the whole experience. Being able to switch b…

  self: super:
  
  let
    callPackage = super.callPackage;
  in {
    darktable = callPackage
      ./pkgs/darktable { inherit (super) darktable; };
  }

  { darktable, fetchurl, ... }:
  
  darktable.overrideAttrs (_: rec {
    version = "3.0.0";
    src = fetchurl {
      url = "https://github.com/darktable-org/darktable/releases/download/release-${version}/darktable-${version}.tar.xz";
      sha256 = "7195a5ff7ee95ab7c5a57e4e84f8c90cc4728b2c917359203c21293ab754c0db";
    };
  })

Post by therein » Wed, Apr 15, 2020, 9:37 PM UTC

rtu8lu wrote: post #51

therein wrote: post #47

Earlier quoted context omitted.

I made the switch from Arch about a week ago. So far, great experience. I love the fact that my system state is reproducible and if I use version control on my dotfiles, I basically have a full backup of the look and feel of my workstation. VFIO with GPU passthrough works flawlessly. Setting up FDE with LUKS during and after the install was a breeze as well. Really enjoyed the whole experience. Being able to switch b…

I have something like this in my overlays.nix: self: super: let callPackage = super.callPackage; in { darktable = callPackage ./pkgs/darktable { inherit (super) darktable; }; } And my default.nix in pkgs/darktabele looks like this: { darktable, fetchurl, ... }: darktable.overrideAttrs (_: rec { version = "3.0.0"; src = fetchurl { url = "https://github.com/darktable-org/darktable/releases/download/release-${version}/d…

  self: super:
  {
    electrum = super.electrum.overrideAttrs(old: rec {
      preBuild = old.preBuild + ''
        # Patch unnecessarily tight dependency on ecdsa version
        substituteInPlace ./contrib/requirements/requirements.txt --replace 'ecdsa>=0.14' 'ecdsa>=0.13'
  
      additionalInputs = with super.python37Packages; [
        python-jsonrpc-server
      ];
  
      propagatedBuildInputs = old.propagatedBuildInputs ++ additionalInputs;
  
      src = super.fetchFromGitHub {
        owner = "spesmilo";
        repo = "electrum";
        rev = "223b62554ead397bb94013c0d9c95b63a0708ea6";
        sha256 = "05djndhdggsw0r9pqn3gnb31nvzghgcsg05r3f7b6hwz84zbl22r";
        fetchSubmodules = true;
      };
    });
  }

Post by golergka » Wed, Apr 15, 2020, 9:46 PM UTC

yjftsjthsd-h wrote: post #27

golergka wrote: post #7

I'm yet to see a backend app architecture that both is elegant and effective from developer perspective and at the same time doesn't push her to make unneccessary database calls for each request when business logic becomes significantly complex.

> doesn't push her to make unneccessary database calls for each request when business logic becomes significantly complex. Are you objecting to holding all state in a database, or something else? If so, the only real alternative is to have individual servers hold state, which seems like a poor choice; one way or another you're going to hit the CAP theorem, and databases are well-optimized for getting you the best res…

Post by CJefferson » Wed, Apr 15, 2020, 10:13 PM UTC

lidHanteyk wrote: post #25

rkangel wrote: post #19

Earlier quoted context omitted.

Do you have any evidence to support your assertion that it was an issue with an organisation rather than the technology? Not all technologies are good. Not all organisations are good. Sometimes it's one. Sometimes it's the other.

Sure. Given code which works for a lot of people, versus some organization composed of people, the fault is probably with people and not with code. This follows from the formal properties of code as mathematical objects, plus the property of probabilistically-checked proofs: If code works for a lot of people, then the code is expected to work generally with high probability. Moreover, there are lots of folks having p…

Post by downerending » Wed, Apr 15, 2020, 10:48 PM UTC

rudolph9 wrote: post #32

I recently switched to NixOS and have essentially configured my OS from scratch in less than a week and now use it as my main system. The thing to remember about NixOS is it’s not a distribution of KDE or Gnome or manager of anything, it’s a declarative way of configuring those things and allows you to easily roll back changes to entire OS. It’s a little bit of investment to get started but one you get rolling it’s s…