francorbacho

joined 1 year ago
sorted by: new top controversial old
It feels so futuristic in c/microblogmemes@lemmy.world
[–] francorbacho@lemmy.world -3 points 1 year ago (1 children)

Direct streaming/downloading doesn't give your IP away (just to the server), torrenting does.

So tired of Adobe. They're part of the problem. in c/firefox@lemmy.ml
Knowledge Transferability in NixOS in c/linux@lemmy.world
[–] francorbacho@lemmy.world 1 points 1 year ago (1 children)

Thanks for the info. Where can I follow/read this discussion?

Can I not use dot in filename for a Rust module? in c/rust@programming.dev
[–] francorbacho@lemmy.world 9 points 1 year ago (1 children)

Dots are not allowed. If it's not too much code, you can use inline modules, otherwise you have to stick to:

action/
    attack/test/
        mod.rs

And then:

mod attack::test;
Knowledge Transferability in NixOS in c/linux@lemmy.world
[–] francorbacho@lemmy.world 1 points 1 year ago (3 children)

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.

14
Knowledge Transferability in NixOS (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by francorbacho@lemmy.world to c/linux@lemmy.world
8 comments fedilink
 

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 nix command, but 1. it doesn't do everything, and 2. it's so new that every single documentation tells you to use nix-env or other specific commands. Why not nix 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.nix makes sense. But this also configures x11, printing services, OpenSSH, pulseaudio. These programs have their own configuration files, that are governed by their own communities.

  • What am I supposed to put into /etc/nixos/configuration.nix? What is the point of reproducible builds if I put every single package I use in environment.systemPackages, which means it has to download gigabytes of data?

  • The error messages are not great. This is specially bad when a lot of the syntax feels made up.

The learning curve for this is absolutely huge, so I was wondering if it was worth spending a month learning all this, when it only applies to Nix/NixOS and I might not need all the complexity that comes with it.

I would love a simpler Nix.

20
Cycling Krakow (lemmy.world)
 

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?