NixOs

That might be the case, but calling their distros good is a stretch.
And they are hell-bent on making them shittier.

>Since you didn't post an actual example I'm going to assume you asked a question thats easily answered in the manual. You've attacked arch and nixOS both on this topic. Maybe the problem is that you refuse to read the manual?
no. People in Arch side actually have a point because they have documentation. NixOS doesnt.

I can name a thing in NixOS that I cannot do on the top of my head, or at least it isnt documented to the point its reasonable

the fact that in nixos everything is handled through these configs, its really really really horrible
and the fact that there is THREE different ways to do stuff
and the fact that there are infinte amount of ways to frick with shit when you start a dev envinronment

you know, this autistic Arch-tier behaviour would be warranted if NixOS wouldnt be 10x more complciated with only 1/100th of documentation

the only reason why nix people boast about "OMG I ONLY DO THIS ONCE AND NEVER TOUCH IT AGAIN BASED BASSSSED!!" is precisely because in NixOS, its so fricking painful to do one thing

>destroy everything in linux
>dont provide any documentation for shit
>get mad when someone questions your project
>tell them to read the non existant manual
>???

go on. Install Hyprland and show your dolphin with breeze dark theme and I will judge if you get it right
Then show me what hoops you had to go through to get it working and then tell me how shit like that happening every now and then is okay for NixOS

nah its not tech support. This thing can only be achieved in Arch but in Nix its really not possible

>https://github.com/andir/npins
it uses fetchTarball which is equivalent to "sorry, I now need to upload your whole 10GB monorepo to the store to be able to run any command" you dumb ape

No shit you have download sources to build a package? But I have my fricking monorepo cloned right there on my disk and I don't need nix develop to fricking copy it each time I run it. And god forbids you use LFS and you end up with useless pointer files in your store because MUH GIT FILTERS IMPURE.

let's say you have a file in your HDD called foo-1.2.3.tar.xz unpacked into foo-1.2.3/ folder
the foo-1.2.3/ will still gets nix store'd into /nix/store/xxxx-source/

to demonstrate, let's try building a simple hello world program
create bar and build.nix in the current directory
cat >bar <<'EOF'
#!/usr/bin/bash
echo "Hello, World!"
EOF
cat >build.nix <<'EOF'
with import <nixpkgs> { };
let
bar = { stdenv }:
stdenv.mkDerivation {
name = "foo-1.2.3";
dontUnpack = true;
dontBuild = true;
installPhase = "install -Dm0755 ${./bar} $out/bin/bar";
};
in
callPackage bar { }
EOF
now build it
$ nix-build --no-out-link build.nix
this derivation will be built:
/nix/store/xxxx-foo-1.2.3.drv
building '/nix/store/xxxx-foo-1.2.3.drv'...
Running phase: patchPhase
...
/nix/store/xxxx-foo-1.2.3
now if you execute /nix/store/xxxx-foo-1.2.3/bin/bar it will print "Hello, World!", but we're not interested in that
what we're interested in is the fact that the bar file we just created gets copied to the nix store
you'd think the installPhase code is gonna be the following while derivation is being build, because bar file is in current directory?
install -Dm0755 /path/to/my/current/directory/bar $out/bin/bar
well, you're mistaken
$ nix-store --print-env $(nix-instantiate build.nix 2>/dev/null) | grep installPhase
export installPhase; installPhase='install -Dm0755 /nix/store/xxxx-bar $out/bin/bar'

as you can see the bar file gets copied first to the nix store before the derivation is being built and after that the build script which is installPhase will use it for any purpose, in our case it gets installed to bin/
so, any file or directory referenced in a derivation will get copied to the nix store no matter what

No duh that referenced paths that get realised are copied into the store. But riddle me this my fellow Black personhomosexuals - I create a simple devshell with `hello` command. Running it via `nix develop` takes ~2s initially, ~1s on subsequent calls. Running it with `nix-shell` (via `flake-compat`) takes ~1s even on first invocation. Ok, whatever, as long as `nix develop` is cached. But then I put a ~6GB file to simulate the chonky work repository. This file is not referenced anywhere in the flake. And lo and behold `nix-shell` still takes ~1s while `nix develop` initially takes ~1 FRICKING MINUTE and then on next invocations, that should've been cached IT STILL TAKES FRICKING ~30 SECONDS. An in a real repo it would've been even worse as it's a shitload of small files that add up to 6G, not one big chonker. It's literally monorepo holocaust, making flakes a joke for this use-case.

Here, reproduce it yourselves:
~/wtf $ cat flake.nix
{
inputs = {
nixpkgs = { url = "nixpkgs/nixos-unstable"; };
flake-compat = { url = "github:nix-community/flake-compat"; flake = false; };
};

outputs = {
self,
nixpkgs,
flake-compat
}:
let
pkgs = nixpkgs.legacyPackages."x86_64-linux";
in
{
devShells."x86_64-linux" = {
default = pkgs.mkShell {
buildInputs = with pkgs; [
hello
];
};
};
};
}

~/wtf $ cat shell.nix
{ system ? builtins.currentSystem }:
let
lock = builtins.fromJSON (builtins.readFile ./flake.lock);
flake-compat = builtins.fetchTarball {
url = "https://github.com/nix-community/flake-compat/archive/${lock.nodes.flake-compat.locked.rev}.tar.gz";
sha256 = lock.nodes.flake-compat.locked.narHash;
};
in
(import flake-compat {
inherit system;

src = ./.;
}).shellNix

TL;DR flakes are fake and gay

lmao, how can anyone treat this shit seriously, what's your response nixsisters?

>Verification not required.

after you commit test4.img to your repo, it'll look something like this
$ git add test4.img && git commit --m blah
[master xxxxxxx] blah
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 test4.img
$ time nix-shell --run hello
this path will be fetched (0.05 MiB download, 0.22 MiB unpacked):
/nix/store/xxxx-hello-2.12.1
copying path '/nix/store/xxxx-hello-2.12.1' from 'https://cache.nixos.org'...
Hello, world!

real 0m44.933s
user 0m2.392s
sys 0m3.543s
$ time nix-shell --run hello
Hello, world!

real 0m1.050s
user 0m0.698s
sys 0m0.185s
$ time nix develop --command hello
Hello, world!

real 0m0.490s
user 0m0.065s
sys 0m0.029s

very fast since it's cached and `nix develop` and `nix-shell` use the fixed repo snapshot that is git rev
or you could just force `nix develop` to never use dirty repo, like this
https://0x0.st/Xoau.txt
or even
nix develop '.?rev=rev' --command hello
where rev is your git rev, you could get the rev using `git log` or `git rev-list HEAD`

Here are my timings for what it's worth:
~/wtf $ time nix-shell --command "hello"
Hello, world!

________________________________________________________
Executed in 940.84 millis fish external
usr time 403.34 millis 239.00 micros 403.10 millis
sys time 174.85 millis 239.00 micros 174.62 millis

~/wtf $ time nix develop --command "hello"
Hello, world!

________________________________________________________
Executed in 2.11 secs fish external
usr time 325.14 millis 256.00 micros 324.88 millis
sys time 180.52 millis 244.00 micros 180.28 millis

~/wtf $ time nix develop --command "hello"
Hello, world!

________________________________________________________
Executed in 903.70 millis fish external
usr time 338.13 millis 221.00 micros 337.91 millis
sys time 156.34 millis 210.00 micros 156.13 millis

~/wtf $ dd if=/dev/random of=$PWD/test4.img bs=1024 count=6000000 oflag=direct
6000000+0 records in
6000000+0 records out
6144000000 bytes (6.1 GB, 5.7 GiB) copied, 48.2053 s, 127 MB/s

~/wtf $ time nix-shell --command "hello"
Hello, world!

________________________________________________________
Executed in 1.04 secs fish external
usr time 378.15 millis 0.00 micros 378.15 millis
sys time 214.13 millis 524.00 micros 213.61 millis

~/wtf $ time nix develop --command "hello"
Hello, world!

________________________________________________________
Executed in 56.23 secs fish external
usr time 1.79 secs 349.00 micros 1.79 secs
sys time 6.76 secs 215.00 micros 6.76 secs

~/wtf $ time nix develop --command "hello"
Hello, world!

________________________________________________________
Executed in 29.35 secs fish external
usr time 1.60 secs 325.00 micros 1.60 secs
sys time 6.52 secs 202.00 micros 6.52 secs

it's because your work repository is cluttered you fricking moron, wtf why are you so dumb
it'll become faster if you git add test4.img && git commit -m blah
why is it faster? because `nix develop` and `nix-shell` now use the fixed snapshot of your git repo, i.e. HEAD
when it was cluttered, flake had to scan the entire contents of your current directory, and has to compare each file with the cached hashes and shit
goddamn, I'm speaking to a moron

`git commit` doesn't get pushed to github.com, moron
it's only on your HDD until you `git push` of course
how much of a moron are you?

what do you propose?
git snapshot is similar to tarball, you have foo-1.2.3.tar.xz and then foo-1.2.4.tar.xz and then foo-1.2.5.tar.xz, and so on
the point of flake is to force people to use a fixed version of your codebase, which is just
>just keep copying your codebase someone's HDD bro
>another change? just remove the previous copy and copy a new one bro
sounds like git to me, if you have real job you'd use git
all normalgays who work in tech use git

>my ADHD-addled brain, not the other way round. And shit like this makes it harder.
Found the source of all your problems.

holy kek how stupid are you? not getting git != github is a new low even for a IQfytard

ez don't use gay flakes. they suck and always will, there's a reason the community is split on them. Its like someone decided nix is too good, how can we frick it up by introducing a moronic non compatible model for muuh purity

tranNIX stickers lmao
(I installed nix earlier this week)

let's say you have a file in your HDD called foo-1.2.3.tar.xz unpacked into foo-1.2.3/ folder
the foo-1.2.3/ will still gets nix store'd into /nix/store/xxxx-source/

yeah the internet was just blurrier back then

>uptime: 7 hours something something
cool virtual machine for larping

>meme
cool, make another thread about your broken install or lost data or whatever low IQ problems low IQ's have

rms uses trisquel

it’s not even a fsf approved distro, he’d never touch it

I don't think anyone really cares about FSF distro endorsement except rms. They know nonfree software is just unavoidable for some people (i.e. binary blob hardware drivers) but they don't want to seem like unprincipled hypocrites.