There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

ByteOnBikes ,

Sorry I’m too stupid to understand this joke. Someone explain?

EfreetSK , (edited )
@EfreetSK@lemmy.world avatar

There’s a new trend with immutable distros and they have some pros and cons. OP’s stance apparently is that they’re the future

itsfoss.com/immutable-distro/

demesisx OP ,
@demesisx@infosec.pub avatar

👍🏽

dogsnest ,
@dogsnest@lemmy.world avatar

Does it matter if you prefer emacs or vi, tho’?

ByteOnBikes ,

Oh that’s super helpful and incredible.

I’m not familiar with that side of Linux as I’m primarily a user. But that’s how our devops pipelines work to ship apps/websites. We’re shopping the entire working package with every update, and rolling back with issues. It’s a fantastic system since as a developer, I can isolate problems.

I never thought about that on a OS level. And I support it!

xilliah ,

Changes to a declarative operating system, such as NixOS, are atomic. This allows for easy experimentation and rolling back to older configurations.

For example say you install gimp for editing photos. Normally you’d just install it using command line or a clickidity gui program. But say you don’t like it. Maybe it causes an issue. Then you have to uninstall it again. You are applying yet another action to the same system. That system is mutable, or modifiable, and that introduces some extra complexity.

With NixOS you can simply roll back to the previous state you had before installing it. It also doesn’t have to support stuff like uninstalling. The downside is that it likely uses a bit more resources when changing configurations.

This also applies to stuff like user management, services, e.g. a webserver.

Any experts correct me if I am wrong, I haven’t tried any of these systems yet.

MajorHavoc ,

We’ve known since the 1950s that our configurations should be declarative, to make them resilient to necessary changes to our software stack.

Instead of coding exactly what change needs made, we ought to write a config that declares the intended outcome, and then do extra work to write code that correctly interprets that config. This way when all the commands we used stop working (and they do!), we still know the original intent of the configuration.

But making config management declarative is a lot of work. So fuck that noise. I’ll do it in bash, instead, again.

demesisx OP ,
@demesisx@infosec.pub avatar

Nix actually IS Bash under the hood. It uses Perl and Bash to create an atomic installation. I tend to do a LOT less maintenance than I’d need to do if I rolled everything from scratch in Bash.

marcos ,

Oh, the meme really is about Nix then? I assumed it was about C.

I guess IT has a lot of holding into old ways going on.

ByteOnBikes ,

Is there a article about this I can find more info about this?

It’s a brand new topic for me and I just read this one from a previous comment. And trying to learn more.

bjoern_tantau ,
@bjoern_tantau@swg-empire.de avatar

Luckily with free software there’s always a choice.

onlinepersona ,

Which declarative systems exist besides nix? Don’t say ansible. It’s barely declarative.

Anti Commercial-AI license

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •