Yes, nix complements your system’s package manager, but doesn’t replace it
Yes, nix complements your system’s package manager, but doesn’t replace it
Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒
This is how I would read it. But if you have Mesa do it, it’s in software, and you might just be using a software coded directly then, it’s much easier.
From my understanding, it’s the hardware that produces bad results. There’s no encoding logic in the drivers itself. That’s why the encoding is accelerated in the first place.
E.g. if the hardware doesn’t support b-frames – which for long it didn’t – a new driver won’t do jack. This is just about how video data gets into and out of the card, any encoding logic is handled by the hardware.
Haha I still remember finding that out
God how dumb
What made the release exciting for you?
I just roll along on NixOS-unstable, so for me changes just trickle in over time.
On the last day actually, haha
For anyone interested, this was due to a curl regression AFAIK. 24.11 was supposed to release a week ago but a lot of stuff had to be rebuilt.
Foobar2000
Dang dude, I had just gotten over foobar2000.
Ahh! It was such a step up from Winamp. I think I started using that around 0.7… and actually used it with Wine when I started using Linux as my main OS in about 2008. But there is nothing quite like it.
The only good distribution is my distribution.
Dang
Currently, there’s no serious discussion about removal from mainline. And LTS won’t remove it.
Should it happen, you can still use Kent’s kernel tree as before. Whether distributions ship it - who knows.
If there’s no mainline or dkms support, I’ll move my storage away from it in favor of btrfs that I’ve successfully used the years before instead of switching to LTS. Just because of future maintainability and migration options.
Nobody forced him to apologize. On the other hand, the Linux community isn’t forced to take his patches.
While I understand the sentiment, I’d argue that an apology should be made in the same context as what you’re apologizing for. Kent made his statements on the LKML - if his apology is sincere, I don’t think it’s too much to ask to put it there as well
Who hates ChromeOS? Never heard someone say that
While I do get your sentiment, we currently see in Ukraine what happens if you don’t have a defense industry: You’re reliant on other countries to supply you in case a hostile nation notices that you’re lacking it.
All that follows is my personal opinion, but for ease of writing, I’m gonna present it as facts.
Once you have grasped the advantage that Nix offers, all the fundamentally different solutions just seem s o inferior. When I first tried NixOS on a decommissioned notebook, the concept immediately made sense. Granted, I didn’t understand the language features very well – I mostly used it for static configuration with most stuff just written verbatim in configuration.nix
, though I did use flakes very early on because of Lanzaboote. But just the fact that you had a central configuration in a single language that was able to cross-reference itself across different parts of the system absolutely blew me out of the water. I was a very happy and content Arch user, even proficient enough to run my own online repository that built from a clean chroot for AUR packages (if you use Arch with AUR packages on multiple systems, check out the awesome aurutils!), but after seeing the power of NixOS in action, I switched over all my machines as soon as I could - desktop, virtual servers (thanks nixos-anywhere!), main notebook and NAS.
People often praise the BSDs for their integrated approach – NixOS manages to bring that approach to Linux. Apart from GUIX System that I never tried because Secure Boot was a requirement when I last looked at other distributions, none of them have tackled the problem that NixOS solves, and it’s not even certain if they actually understand it. Conceptually, it plays on a whole different level. No more unrecoverable systems, even with broken kernels – just boot the previous configuration. Want to try changes without any commitment? nixos-rebuild test
got you. Need an app quick? nix shell nixpkgs
it is.
Plus the ecosystem is just fantastic. The aforementioned nixos-anywhere
really helps with remote provisioning, using disko
to declaratively setup filesystems and mounts, you have devenv
which is a really good solution for development environments, both regarding reproducibility and features, and many more that I can’t mention here. There is nothing comparable, and the possibilities are unlike in any other ecosystem.
It’s not perfect for sure though, and documentation is sparse. The language concepts which allow one to “unlock” the most powerful features are different from what most people know.
I was lucky enough to have some downtime at work to get into the system a bit deeper (this was still for work though, just not my core skillset) by implementing a “framework” for our needs which forced me to not just copy and paste stuff, though I definitely did get inspired from other solutions, but to actually better understand the module system (I think?), thinking in attribute sets, writing your own actual modules, function library and so on. But in the end, it was definitely worth it, and I’m unaware of any other system that would allow what Nix and NixOS allowed me to build.
NixOS […] some packages are kinda old
Fair
that server will be going back to debian next summer.
I don’t think that will solve the “some packages are kinda old” issue.
I’ve played the game shortly hoping for it to be a mix between Isaac and Noita. However, the game failed to grab my attention for longer, as the wand building mechanic is way inferior to Noita, though the custom wand properties sure are nice, and remaining loadout and options were worse than what I remember from Isaac.
All this doesn’t obviously mean the game is bad, apart from maybe the cringe story. However, measured against the giants - I’d also include Enter the Dungeon here for presentation - it currently falls short.
so much for the tolerant left
Unfortunately, from my testing back when I used Arch, a lot of packages in the AUR didn’t meet packaging guidelines, so while quickly writing a PKGBUILD is easy, writing it correctly requires a bit more effort, especially regarding the dependencies. IIRC
namcap
is often enough, but ideally packages should be built in clean chroots as well to make sure they build everywhere