4 ms·

if you know nix DSL but dont know cpp (whatever it means to know cpp) then the whole nix internals are just a black box to you. this is simply not the case with

if you know nix DSL but dont know cpp (whatever it means to know cpp) then the whole nix internals are just a black box to you. this is simply not the case with guix. if you cant see the benefit of guix/guile relationship here then there is not much more i can say to you anyway as i said at the start this whole thing is just heads banging against a wall. i have no problems with you holding your views. it just happens that i disagree with them. if you expect of me to promote the virtues of lisp to you then im sorry but thats not gonna happen. you can do your own discovery. if you dont know then you dont know :)

cmm 3y ago
> the whole nix internals are just a black box to you. Yes, and just as well. Modern software is a barely-holding-together tower of abstractions as it is. Do you find yourself looking at the C source of Guile's runtime often? Or Glibc? The Linux kernel? Intel microcode? Aren't you glad you don't have to? (Nixpkgs, on the other hand, is very accessible and many parts of it make for great reading) > if you expect of me to promote the virtues of lisp to you then im sorry but thats not gonna happen. No, I hope (in vain, looks like) that you'll start making some sense and stop using and then desperately defending stupid arguments.
- medo-bear 3y ago
  lol so now you think that looking at nix internals is like looking at intel microde. my hat goes off to you :)
  - cmm 3y ago
    Looking at Nix internals would, over at the Guix land, be more like looking at the Guile compiler, or garbage collector -- all Nix-the-tool implements is the language and the primitive derivation machinery. Could certainly be educational, but neither is nor should be required of anyone _using_ the abstraction in question. Do you have any more deliberate obtuseness to share, or shall we stop?
    - medo-bear 3y ago
      > Looking at Nix internals would, over at the Guix land, be more like looking at the Guile compiler, or garbage collector huh? nope. looking at guix internals would just mean looking up guile documentation :)

cmm 3y ago

> the whole nix internals are just a black box to you. Yes, and just as well. Modern software is a barely-holding-together tower of abstractions as it is. Do you find yourself looking at the C source of Guile's runtime often? Or Glibc? The Linux kernel? Intel microcode? Aren't you glad you don't have to? (Nixpkgs, on the other hand, is very accessible and many parts of it make for great reading) > if you expect of me to promote the virtues of lisp to you then im sorry but thats not gonna happen. No, I hope (in vain, looks like) that you'll start making some sense and stop using and then desperately defending stupid arguments.

medo-bear 3y ago
lol so now you think that looking at nix internals is like looking at intel microde. my hat goes off to you :)
- cmm 3y ago
  Looking at Nix internals would, over at the Guix land, be more like looking at the Guile compiler, or garbage collector -- all Nix-the-tool implements is the language and the primitive derivation machinery. Could certainly be educational, but neither is nor should be required of anyone _using_ the abstraction in question. Do you have any more deliberate obtuseness to share, or shall we stop?
  - medo-bear 3y ago
    > Looking at Nix internals would, over at the Guix land, be more like looking at the Guile compiler, or garbage collector huh? nope. looking at guix internals would just mean looking up guile documentation :)