Fonzie!

I get that it’s less secure, but using verified flatpaks beats homebrew by a large margin.

Shame they didn’t mention that homebrew is a security nightmare and will happily download maliciously modified code

That’s so true, I was missing this part! With homebrew you’re at the mercy of whoever put the package out there, much like with installers (and nix to be fair)

Edit: omg then the author claims flatpak is better for security?!? It has the same nightmare security issues.

LMAO no‽ Flatpaks can be verified, and you can choose not to install unverified flatpaks (which you should!) They are also containerised pretty well by default, in case they’re malicious!

I’m just happy my boi nix got a shoutout.

I love having a packages file and a lock file, both user-specific rather than system-wide, offering reproducibility, stability and a good, central place where I can see what I did to debug.

Nobody said anything about the init system, though.

Woah! What a racket!

The bottom bit looks like Loss; :.|:;

Dank Memelord

To add to @ParetoOptimalDev@lemmy.today

The uutils are MIT licensed, simply put it means “do whatever you want with it, as long as you credit us”.
The coreutils are GPL, simply put “do whatever you want with it but only in other GPL works, also credit us”.

The coreutils make sure forks will also be open source.
While the uutils aren’t closed source, they do allow you to make closed source forks.

The uutils’ license is too permissive.

I don’t mind using it for larger teams, it can be great for organised communication such as dev teams!

But it shouldn’t replace documentation.

(Also, Discord itself is a proprietary, censoring telemetry wasp nest, your FOSS dev team shouldn’t be organised in it but Matrix, XMPP, IRC channels or something else open.)

Likely not anytime soon as they tend to hold off latest features and prefer older (but maintained) LTS versions of just about everything. Also especially not if it turns out to be a bad idea; they explicitly build Mint without Snaps since their inclusion in the Ubuntu base.

Mainly memory safety; split (which is also used for other programs like sort) had a memory heap overflow issue last year to name one. The GNU Coreutils are well tested and very well written, the entire suite of programs has a CVE only once every few years from what I can see, but they do exist and most of those would be solved with a memory and type safe language.

That said, Rust also handles parallelism and concurrency much better than C ever could, though most of these programs don’t really benefit from that or not much since they already handled this quite well, especially for C programs.

uutils/Linux?

What is this table from? Is it from some website?

Yeah, but it shouldn’t replace forums.

Isn’t that just a bandwidth issue?

This is the way.

Sure, ok, that’s still my daily driver, it’s incredibly stable (and no, it’s not fucking outdated), but other than that it doesn’t help so much against accidentally borking your system.

So in this context, I’m recommending @sockpuppetsociety@lemm.ee NixOS.

May I introduce you to my lord and saviour NixOS?

And not somehow break it more from there? Impressive!

I can see how you were confused, but maybe don’t phrase it like that next time lol.

That’s true, I’ll keep it in mind! I thought I was being funny but I was just confusing and crude