While you do have a fair point, I was referring to the case where one is basically implementing a map operation as a for loop.

Technically this is also possible with for loops, like with OpenMP

Compiler optimizations like function inlining are your friend.

Especially in functional languages, there are a lot of tricks a compiler can use to output more efficient code due to not needing to worry about possible side effects.

Also, in a lot of cases the performance difference does not matter.

Also surely a lot of people would know tar -Create Ze Vucking File and/or tar -Xtract Ze Vucking File

You mean that instead of having a binary blob you have a generator for the data?

Dogmatic statements like this lead to bad, messy code. I’m a firm believer that you should use whatever style fits the problem most.

Although I agree most code would be better if people followed this dogma, sometimes mutability is just more clean/idiomatic/efficient/…

Did you truly read what I said? The only logical way I can frame your comment is that you glanced at what I wrote down and started writing a reply.

To a regular average windows user, ubuntu is incredibly complicated. When you learm how it works and how you’re supposed to use it, it becomes incredibly easy. The “hard” part of ubuntu is the paradigm shift from windows to the linux ecosystem.

Similarly, to an average linux user nixos is “hard” because it does things completely differently from other linux distros. But once you’re used to it, it just makes sense and is easy.

So the comparison is average windows user -> ubuntu vs average linux user -> nixos. Not average user -> ubuntu vs average user -> nixos.

Finally: Nixos documentation is IMO 100x better than ubuntu documentation. Whenever I experience any issue with ubuntu it’s easier to just load up the arch wiki and hope it’s similar than it is to try and find anything specific for ubuntu that isn’t either 10 years out of date, a massive gaping security risk or just plain dumb. The nixos wiki may not be perfect but it has always been sufficient for my needs, and I have to run a decent amount of very niche pieces of software.

It’s incredibly complicated in the same way that ubuntu is incredibly complicated to a lifelong windows user.

It just requires a bit of a paradigm shift which includes a learning curve but IMO once you’re past that point it’s intuitive and even easier than other distros.

https://nixos.wiki/wiki/Linux_kernel

You can specify custom parts of the config that enables that module and/or extra module packages.

If you specify a custom part of the config then ye sure you’ll be compiling the kernel on each kernel update but you don’t need to manually configure it

The killer feature is declarative system management. Reproducible systems is just one of the resulting properties. You want to just try out KDE for a week coming from gnome? Good luck getting rid of all the bloat when switching back on arch. You want to run a program once but not necessarily have it installed on your system? You can do that with nixos. You messed something up and your system now doesn’t boot? You can go back to a previous iteration with nixos, no need to find your liveUSB to start messing with chrooting and stuff. Ever find yourself asking where the configuration file for is so you can edit it? The answer is /etc/configuration.nix Ever had to merge older configs with newer ones because the software updated? (If no, you haven’t been using arch for long) why would you need to do that? You declaratively specified how you want your system to behave and nixos will figure out how to translate that to the new config.

And that’s just the “killer” features I use on a day to day basis

Bwoah

But rust

What is this recent trend of saying “batteries included” for literally anything software related?

It feels like it tells you nothing at all about the project except that whoever is talking about it is big into buzzwords

Hehe pp