Hey at least we got the CEO of a Saudi oil company heading up the climate talks. I’m sure that he’s perfectly willing to set aside his own personal interests and take one for the team and reduce his profits by leaving Saudi oil in the ground, and encouraging (or even requiring???) everyone else to do the same, right? Right?
Another NixOS user (and minor package maintainer, if it matters) here. Essentially, NixOS is actually rather simple to write a configuration file for a particular program once you get the knack for the nix language and learn how to workaround the sandboxing. I would actually consider it substantially less involved as compared to (for instance) creating your own Debian package.
However, getting to this point will take a bit of effort, and this step is more or less obligatory to use software on NixOS, whereas it generally isn’t (but still is a good idea) on other distributions.
The single killer feature that convinced me to move to NixOS is the ability to very easily keep separate development environments separate. For instance, if you’re working on multiple dev projects that have different minimum requirements, and you want to ensure that (for instance) you don’t accidentally use features from after boost 1.61 for project A, because that’s the stated requirement, but you need features from boost 1.75 in project B.
In a normal distribution, in order to set up an environment that has the proper version for project A you’d need to set up a chroot, a virtual machine, a complicated set of environment variables in a bespoke script with custom installation paths that you need to set up manually and remember to source, or just install a newer version of boost and rely on continuous integration to catch it if you screw up.
In NixOS, you can set up different shells which all reference the exact correct version of the libraries required for every project, you can have them installed simultaneously and without conflicts, and there’s even a shell hooking program that will automatically load and unload this configuration when you change directories into and out of the project folder. It makes managing many different projects much easier. It’s like a better version of venv, but for everything.
The shittiest thing is that they’re not actually good at it. We generally use compactness as a proxy for a gerrymandered district. However, you can effectively gerrymander using extremely compact districts. youtube.com/watch?v=Lq-Y7crQo44
This is terrifying, and a strong reason to move to multimember districting.
Did you know that this information can be easily googled, and you don’t have to double down? A writable CD most typically contains between 650 and 700 MB of capacity.
Does this scope do Fourier analysis? If so, can you see which frequencies are being suppressed? Does this suppression at this frequency also occur with generated white noise?
$1 grilled cheese (mander.xyz)
World facing ‘hellish’ 3C of climate heating, UN warns before Cop28 (www.theguardian.com)
Boy howdy! (lemmy.ml)
Comparison between NixOS vs blendOS vs Vanilla OS: what to pick and why?
So I’ve recently taken an interest in these three distros:...
Who's That Pokémon? (lemmy.dbzer0.com)
lots of homework.... (feddit.de)
Siglent SDS1104XE: slanted square wave (imgur.com)
Hi!...