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/)TT
trevor (he/they) @ trevor @lemmy.blahaj.zone
Posts
0
Comments
451
Joined
2 yr. ago

  • While I generally agree with your skeptical attitude toward this, I think the fact that they were targeting Apple's Metal graphics API to built the most performant possible IDE makes sense. You can't just snap your fingers and have a Linux graphical stack start working with your software.

    I think the reason they targeted macOS first is probably because many of the dev team uses Macs.

    As a Linux user, I'll happily wait for software like this to get ported to native Linux APIs so we get performant text editors instead of more Electron crap.

  • Fair. I used it when the project was still very new and was basing that statement off of my admittedly flawed perception of time.

    Thankfully, due to quirks of language, we have to say "1.5 years", so it's not technically incorrect :p

  • It's not about being eaten to extinction, obviously, but nice.

    If you consider cultivating new zoonotic diseases and pandemics into existence and wasting energy and resources on feeding animals the nutrients that humans can more efficiently benefit from directly to be "sustainable", then I think it's you that is using a definition of sustainable that is different from what is commonly understood.

  • Here's what I do in my docker images:

     
        
    mkdir -p /lib-your-executable
    ldd ./your-executable | tr -s '[:blank:]' '\n' | grep '^/' | xargs -I % cp % /lib-your-executable
    
      

    Essentially, it's the same thing that you're doing, just automating getting the dependencies, and then copying everything in the lib-your-executable dir to your LD_LIBRARY_PATH. I don't know of a better way, other than statically-linking the binaries.

    EDIT: fix typo in commands.

  • Sandboxing does nothing for social-engineering attacks, which is what many of the malicious snaps were designed for.

    And the thing that makes the Snap Store uniquely bad is that there's no human review. Anyone can throw up a malicious snap, and there are very good odds that it'll get served there. Even the Flathub, a community-run project, has human reviews before new apps get published. Canonical, despite having money and resources that community projects don't, can't seem to be bothered to take basic steps to protect their users.