Hello, tone-policing genocide-defender and/or carnist 👋
Instead of being mad about words, maybe you should think about why the words bother you more than the injustice they describe.
Have a day!
I prefer this as well, but just adding that Fish also supports $() for those that don’t know.
I keep hearing people that haven’t used modern versions of Fish say that it’s somewhat different from Bash and strays from POSIX compatibility quite a bit. While the latter is true, Fish has added many bash-isms over the years, so most scripting idioms you’re familiar with will work there too.
Wrong. Have to start adoption somewhere, and doing it in a non-LTS release is a great move.
Same.
The detractors of this project portray it like it’s a far-off pipe dream to be a drop-in replacement for GNUtils. Meanwhile, it’s still a relatively young project that already has 85% compatibility. I think we can do it. Lol.
You’re a different kind of VM enjoyer than me, and that’s okay 😎 I’m glad GNOME Boxes and virt-manager are getting the job done for you. I’m okay with the latter, but I think it needs some love, which is why I’m eager to see alternative frontend options.
Docker works. Podman requires a ton of workarounds and wastes my time. I hope it gets good one day, but I’m not reverting to using systemd to manage containers.
This isn’t just VirtualBox. It’s VirtualBox with a KVM back end. So you get the performance of KVM, but with a much better GUI than virt-manager.
Well, MIT projects can be forked into a new GPLv3 project, right? If Canonical cared, they could have done that to assuage this concern.
I think it’s a valid concern. Pushover licenses are bad. But even if a GPL Rust coreutils project exists (I actually have one, but I don’t have the same goals), it seems unlikely that Canonical would be bothered to pivot to it.
Ah, to live in a world without JavaScript and weird, Nazi crypto dipshits 🥰
As an avid Helix user, thank you for linking this! I had no idea this was available, nor that I wanted it in the first place, but now I do.
Thanks for sharing! Bounds checks are a fair critique. The Rust Performance Book suggests that bounds checking has little performance impact compared to many other factors that you could optimize out, but it’s certainly not zero performance impact, as I initially claimed.
Unless you’re talking about some sort of reference counting, which has to be explicitly added by the programmer in cases where doing so is required for memory safety, I’m not sure what runtime checks you’re referring to?
From what I’ve seen, the performance of programs written in C and Rust are generally the same, more or less, with C or Rust coming out on top with roughly coinflip odds in a handful of cases. This feels like the primary differentiator in performance really comes down to the implementation of the person writing it, and less to do with any performance differences inherent to either language.
This is an awesome tool, and I love to see it get a Rust rewrite.
But the one thing I really wish it could do is embed properly in GitHub’s markdown UI so that when I click them in READMEs it doesn’t have to send me to the asciicinema site.
I’m sure that has way more to do with GitHub than it does asciicinema, but still, that’s why I don’t use it for my projects. I hope that can change one day.
“Thing I say is good, is better than thing I say is mediocre.”
Indeed.
This is not true. If you know Rust and C equally well, you’re likely going to write equally performant Rust.
You could say that Rust is harder to learn than C. I’d disagree based on my personal experience, but you wouldn’t be wrong.
I have no idea how. I write better Rust than I do C 🤷♂️
Rust and C are basically identical in terms of performance (more or less). Idk where the myth that Rust is somehow less performant than C came from.
The ill-informed Rust hatred goes in the Phoronix comments. Rust isn’t inherently slower than C. This was a bug.
So many Rust projects are dual-licensed under Apache or MIT. It’s just a convention that many Rust projects have adopted. Yes, it’s true that there’s nothing intrinsic about Rust the language that requires a certain license type. But it doesn’t mean that the Rust community hasn’t adopted a convention of licensing with pushover licenses. That’s my point.
Using Rust != required to use pushover licenses. It’s just a bad convention that a lot of Rust projects adopt.
If you’re expecting stability for any Ubuntu release, that went out the window when Canonical started forcing Snaps.
But non-LTS Ubuntu releases have always been a testing ground for less-than-stable changes. uutils is just one of them, and the only way to make them stable is to see how they’re being used in the wild.