![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/53fa9c8b-f101-435f-b48a-f89bdb9a990c.png)
I guess you’re under 30 then. It was big post-9/11, in the “freedom fries” era. But it was mostly just used sarcastically to mock the sorts of people who had those kinds of attitudes
I guess you’re under 30 then. It was big post-9/11, in the “freedom fries” era. But it was mostly just used sarcastically to mock the sorts of people who had those kinds of attitudes
Yeah, it has all the same problems that (pre-Musk) Twitter did. Centralization was never the problem, turns out. IMO it’s just the basic central premise that everyone is talking to everyone, all the time. When your brain does that, it’s called a seizure.
Plus tons and tons of furries, which like… you do you, but it becomes a huge ongoing effort just to keep furry porn out of a lot of the feeds, if that’s not your bag.
It’s like a Nathan Fielder production, where the mere fact of its existence amounts to its own kind of performance art piece, outside of the art of the thing itself.
Like how could such an object come to exist in the world? It stretches the mind in whole new directions.
Now you’ll have a zillion users trying to install software in ways that violate all the assumptions that NixOS operates on, but which are still tightly coupled to your NixOS config. Now updates to your system, or even seemingly unrelated config changes (through some transitive dependency chain) can easily break that software.
So now we’ve basically removed half the advantages that motivate Nix/OS in the first place, and when stuff breaks it will look like it’s Nix’s fault, even if it isn’t.
On the other hand, nixpkgs is already the most comprehensive repository of system software out there, and for 99% of packages Nixifying it is pretty trivial. Hell, my NixOS config does that for 3 different GitHub repos right inline in my config.nix
The bashrc poisoning thing was sarcastic. the point is it’s not important as an attack vector because if that’s even part of your surface area, then the attacker is already pretty well into your system
If your system uses 3 different Pythons as dependencies of different packages, which one gets to be /usr/bin/python?
Not sure about 1, but 2 and 3 both have the same answer. Both TSInstall and Mason are just trying to install other software packages on your system, and you’re on NixOS, so of course they can’t do that. You don’t install your software, you declare it. Add the Treesitter parsers you need right next to your plugins (there is a sub collection under the vimPlugins collection just for Treesitter parsers), and put whatever Mason would be installing into your user packages instead.
That said, I agree with the other commenter. Even though the community has done a lot of work on rich config options for Neovim, they’re just too far away from the normal way of doing things in the Neovim world, and plenty of plugins are written in ways that assume it’s configured in “normal” ways. Plus configuring Neovim is already kinda like assembling your own car from parts in any case, so it’s honestly better to just use nix to install Lazyvim or whatever flavor of choice and let it handle the plugin management/config. And believe me, I really tried to do it all in Nix, I wanted to do it that way. But it’s just not worth the headache at this point
deleted by creator