Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T

trevor (he/they)

@ trevor @lemmy.blahaj.zone

Posts
0
Comments
480
Joined
3 yr. ago

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!

  • Canonical does a lot of bad shit, but switching to uutils is not one of them. The "challenges" are expected because it's going in a non-LTS release, which is basically meant to be a beta of the next LTS. And those challenges are being quickly addressed as they're being surfaced. This is exactly the right way to introduce something new, IMO.

    I don't like the uutils pushover license license though :/

  • Because their sandboxing format subtly breaks so many applications (more than flatpak) and Canonical very nefariously co-opts your apt install <package> with a deb package that's actually a stub to install the Snap version, so when your shit breaks, you can waste hours before you realize that they fucked your installation.

    Beyond that, Snap cold start times (installations or updates) are slow as shit (yes, even with LZO compression), and since each snap application can update on its own, you'll also encounter random times when your shit appears to "freeze" but what's actually happening is Canonical is busy polluting your loopback devices to decompress their shittified version of your app.

  • Canonical, being demons, have Snapified things like GNOME, so even your desktop environment will be encumbered by that dogshit packaging format.

    Do not use Ubuntu if you value your time and well-being.

  • Well, for one: no Rust SDK 😭 This is a half-joke. I'd make some apps for Proton, but I'm not touching JavaScript to do it.

    Hopefully, they make more language bindings. I saw that C# was planned, so hopefully they keep the language bindings coming as they stabilize their SDK.

  • Pedophile defender, Ted Cruz, doesn't want you or your children to have privacy. I wonder why...

  • I miss when Docker was putting out new features for containers instead of this shit.

  • Rapist's mentality.

  • Can we avoid calling taking action against valid moral objections "drama"? It only serves to make the people doing the right thing sound like they're being immature, even when they're obviously right.

    Objecting to a fascist government's influence over very powerful build infrastructure used around the world is the right thing to do.

  • This type of comment is indistinguishable from the low-tier, rage bait comments under every Phoronix article.

  • oniux might be exactly what you're looking for.

    It was still in early development when I played with it months ago, so I'm not sure if it's ready for daily usage, but it's from the Tor Project team themselves, so I imagine it will only keep getting better.

  • Lol. No.

  • If this works out, it's likely something that container engines would take advantage of as well. It may take more resources to do (we'll have to see), but adding kernel isolation would make for a much stronger sandbox. Containers are just a collection of other isolation tools like this anyway.

    gvisor already exists for environments like this, where the extra security at the cost of some performance is welcome. But having support for passing processes an isolated, hardened kernel from the primary running Linux kernel would probably make a lot of that performance gap disappear.

    I'm also thinking it could do wonders for compatibility too, since you could bundle abandoware apps with an older kernel, or ship new apps that require features from the latest kernel to places that wouldn't normally have those capabilities.

  • 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.

  • The --stream functionality looks very useful as well. Super cool!

  • 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.