For what it's worth, I don't understand the nix language or all the package manager functions in their entirety. I generally use what I need and that's it. Most information I've required that is nixpkgs-specific I was able to find in the manual. home-manager has one as well and it's been the best reference for me.
sickday
joined 2 years ago
If so, how does that solve the problem of clutter in $HOME ?
If it wasn't clear from my message, the problem(s) these tools are solving for me would be 1. not having to keep track of my dotfiles and their directories, and 2. not storing configuration files directly on the disk I use for the $HOME dir. I'm not claiming these tools would solve clutter in the $HOME dir. Further, I think it should be alright for me to share tools for managing configuration files in your home directory in a discussion that directly relates to that subject.
So you create a symlink from $HOME/.program.ini to something in the nix store?
Normally it's the other way around. When you use nix and home-manager, you're technically generating files that will live in the nix-store and nix/home-manager will take care of symlinking those files to locations in your $HOME dir.
In this scenario though, I would use the https://nix-community.github.io/home-manager/options.html#opt-home.file option from home-manager to create a symlinks to a location that's outside of my $HOME dir so those files don't have to live on my home disk.
My particular use-case is that I want persistent configuration files that are shared throughout a handful of devices on my network. To this end, I use some home-manager symlinks that lead to a network folder where all these various directories and configuration files actually live. I edit those configurations in a single place and their changes propagate across the network to all the devices that would use them.
You can manage symlinks pretty easy with home-manager. I'd personally setup symlinks for these app configuration directories if I don't want them storing files directly on the disk I use for $HOME. It's also done in a delcarative way that can persist across multiple computers.
Wizards of the Coast
Or they can keep using the same engine with the same issues because gamers will definitely buy their next title en-masse despite the previously mentioned issues. Eg. Starfield
What an interesting year. This has to be the 4th or 5th large tech-centric company that's
- introduced some really shitty policy
- pissed off it's consumers
- then backtracks to some degree after backlash
Just like every other company that's done this, the backtrack is likely meant to appease the consumers before the policy gets re-introduced later. Perhaps with slightly different wording.
Mega man Star Force
The Midas Touch of Shit at it again
I posted the list of alternatives simply because OP asked for forks.
What’s wrong with Firefox
Me posting this list shouldn't be an implication that I believe Firefox to be bad. I'm offering alternatives as the OP requests.
and how do the forks address those points?
Every one of the links I shared have detailed information about how their product mutates the original Firefox or Chromium browser. Do you really need me to copy-paste that information into a comment?
Not the OP, but here are some alternatives anyway.
Firefox:
Chrome:
sickofit