Thanks for the info. Where can I follow/read this discussion?
Dots are not allowed. If it's not too much code, you can use inline modules, otherwise you have to stick to:
undefined
action/
attack/test/
mod.rs
And then:
undefined
mod attack::test;
Sorry, but I don't believe it will get simple. And you can't expect people to believe it is "transitioning" when talking about a 20 year old project. I would love to, but I don't think it's realistic.
I did look into GNU Guix but I discarded it because it looked like it had the same problems, and IIRC did not have build cache.
Knowledge Transferability in NixOS
I've been recently getting into NixOS, and I really like the concept of the store, reproducible builds, and declarative configuration. It keeps things organized and clean. But there are certain aspects of its implementation that are kind of rough:
- It feels artificially complicated. Too many commands that do very small changes, unfamiliar configuration files with new, very specific and confusing syntax. Combining all commands into a central, consistent command (like git does) would help tremendously. I am aware of the
nixcommand, but 1. it doesn't do everything, and 2. it's so new that every single documentation tells you to usenix-envor other specific commands. Why notnix rebuild switch? It feels like they tried to separate Nix from NixOS when they could really be the same thing. - Special treat to special packages. Configuring the boot loader, networks, timezone, kernel modules in
/etc/nixos/configuration.nixmakes sense. But this also configures x11, printing ser
Cycling Krakow
I will be living in Krakow next year, and it's quite a big city, so I might need to get a bike to get around. How bad is it to ride a bike, especially during winter? Is the snow going to be a problem?