[-] atomicStan@programming.dev 3 points 3 days ago* (last edited 2 days ago)

Yeah, NixOS is excellent. But, for nix (or close enough) to be the future, an upgrade path should exist for other distros. But, for some reason, I don't really see any such efforts. Like, where are the nix-variants of other distros?

FWIW, Bootcrew has created bootc-variants of many other distros. And, even before, both Endless OS and GNOME OS offered examples of non-Fedora distros with ostree.

EDIT: TIL

[-] atomicStan@programming.dev 2 points 3 days ago* (last edited 3 days ago)

Perhaps I should have been more clear. My apologies. I wanted to draw attention to the fact that -in the case of Fedora Atomic- layering remains a necessity (for most users). This thread goes over it in more detail.

flatpak

Technically speaking, the flatpak format isn't even as limited as some make it out to be. For example, software like Bottles have offered CLI/TUI functionality through it. But Flathub, its most popular storefront, does put a limitation on submissions. Which means that it's effectively not even competing with other package managers that (conventionally) try to offer a broader set of software.

Furthermore, even if the flatpak package exists, not all functionality is retained. For example, the situation around native messaging is still a mess. This prevents e.g. your flatpak browser from communicating with your locally installed password manager. While a(n ugly) workaround exists, it’s quite maddening that it hasn’t been resolved in all these years 😅.

distrobox/toolbx

This is actually a mess. See this comment elsewhere under this post for a bit more elaboration.

[-] atomicStan@programming.dev 3 points 3 days ago* (last edited 3 days ago)

I didn't really mean it in the sense that the communities of different atomic/immutable engage regarding the trade-offs associated by their respective methods of achieving atomicity/immutability. And, honestly, I'd actually love to see more of that. Even if NixOS users would dunk on the rest, at least until the learning curves are brought up.

Instead, what we often find are unproductive threads like this one 😅. In which, naysayers and proponents act like they're engaging, but I simply fail to understand what's happening.

[-] atomicStan@programming.dev 4 points 3 days ago

Not the person you asked. But the only thing I can think of, would be how the flatpak's sandbox might cause friction. Most of the time, you won't even notice it. But, once every while, it shows its ugly face.

For example, the situation around native messaging is still a mess. This prevents e.g. your flatpak browser from communicating with your locally installed password manager. While a(n ugly) workaround exists, it's quite maddening that it hasn't been resolved in all these years 😅.

[-] atomicStan@programming.dev 2 points 3 days ago

IIRC, historically, it was (one of) the first to do so. It took a significant time for (most^[Slackware, famously, continues to not have a dependency resolver. Though, they got their reasons.]) others to catch up.

still

Maybe. I honestly don't know either.

[-] atomicStan@programming.dev 3 points 3 days ago

Many different solutions exist, even native ones. But I'd have to mention Sandboxie as probably the most popular option.

[-] atomicStan@programming.dev 2 points 3 days ago
  • Step 1. Upgrade to proactive security. Projects like HotCakeX' offer a streamlined method of attaining it.
  • Step 2. Commit to best practices. There's a long list of this, but the short of it would be:
    • Uphold a strong backbone of secure software that has proven to be committed to safe practices.
    • Ensure that your system and/or software is always up-to-date.
    • Don't visit unsafe/untrusted websites. Don't click on shady/untrusted links.
    • Don't execute untrusted/unsafe files. Especially not with administrator's rights.
    • Sandbox all activities. So that even if you're compromised, that the adversary can only access very little beyond the binary/program/software itself.
[-] atomicStan@programming.dev 8 points 3 days ago* (last edited 3 days ago)

uses apt

May I ask why you seem to be married to the use of apt?

~~Just couldn't pass up on the opportunity to insert this banger.~~

[-] atomicStan@programming.dev 2 points 3 days ago* (last edited 3 days ago)

First of all, I’m sorry I can’t provide you with a video; I tried attaching it to the post but won’t let me attach any other than photos.

Gifs work. There are some pointers over here.

[-] atomicStan@programming.dev 14 points 4 days ago* (last edited 3 days ago)

You seem to have the false notion that corporate distros are safe (or something). But, that's not true. Look e.g. at the demise of Clear Linux OS.

For (perhaps) a better assessment on whether a distro is well-established^[I.e. that it will not cease existing overnight.] or not, consider looking at the following factors:

  • How long does it exist? Like, if it's old enough to drink, then that's definitely a good indication.
  • How strong is its community? If there are literally millions of users, many of which actively contribute, then that's definitely a good thing.
  • How active is its development? The Linux landscape is constantly evolving. Hence, adopting changes (or, at least, enabling them) is somewhat to be expected.
  • Does it serve a distinct raison d'être? It simply has to offer a strong justification for its existence.
  • Does it have any strong dependencies/contingencies? Here, a lack thereof is actually what's good.

TL;DR: If you want to be absolutely safe, then I'd recommend Arch, Debian or Gentoo.

view more: ‹ prev next ›

atomicStan

0 post score
0 comment score
joined 4 days ago