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/)BC
Posts
10
Comments
367
Joined
2 yr. ago

  • Yay. My first ad-masquerading-as-a-genuine-post experience on Lemmy!

    Thus, we’ve developed a cargo extension that transparently queries the Phylum API for information about a package before it’s allowed to build.

    Only our malware-like behaviour is blessed. Because it's a feature. And research-based. And security-oriented. And commercial! We told you about it beforehand and sold you the idea.

    Assuming the malware discovered is not theirs too.

  •  
        
    bsdtar tfv ᐸ(curl -sL https://static.crates.io/crates/serde_derive/serde_derive-1.0.183.crate)
    
    
      

    Edit: Ogh, using which is a replacement character because Lemmy escapes the real one. This is annoying.

    There, you will see that this file exists:

     
        
    -rwxr-xr-x  0 0      0      690320 Jul 24  2006 serde_derive-1.0.183/serde_derive-x86_64-unknown-linux-gnu
    
      

    Yes, that's a pre-built binary in the crate source release. It's that bad.

  • I hate that I'm linking to Reddit, but I'm just reminded of this.

    Some of us knew where all the obsession with dependencies' compile times will lead, and triggered the alarm sirens, if half-jerkingly, years ago.

    Compile times, and more specifically, dependencies compile times, is and has always been the most overblown problem in Rust. We would have some sort of sccache public repositories or something similar by now if it was that big of a problem.

    And yes, I'm aware proc-macro crates in particular present unique challenges in that field. But that shouldn't change the general stance towards the supposed "problem". And it should certainly not trigger such an obsession that would lead to such a horrible "solution" like this serde one.