The --stream
functionality looks very useful as well. Super cool!
trevor
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.
One thing I really miss from Unity is the efficient use of the top bar doubling as a title bar for full screen windows. I wish modern DEs would do this.
Just here to add that, yes, Snaps are very broken. Do not use them if you value your time or well-being.
The annoying thing is that Canonical dishonestly co-opts your apt
invocations for snap installations, so you're likely to waste hours of your life trying to figure out why the thing you installed doesn't work or takes forever to launch randomly. And they keep Snapifying more of their distro, so even things like GNOME packages are only available as Snaps.
This is the first time I've heard "lint" used this way, but I like it. I've heard Linus refer to various waste left behind on your system as "turds" 💀
Anyway, this looks like a cool tool. Gonna check this out.
I never used erdtree. What do you like about it that is different from eza?
Probably the same shit that Israeli fascists use on Palestinians.
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.