• 1 Post
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle







  • Yup fair point I didn’t know that. Unity presumably does this with dlls that a technical user can easily swap out. In principle an asset store script could do this, but it would be very difficult to verify and enforce so I can see why they’d just ban the license outright as a CYA thing.

    Maybe the answer is to distribute a vlc dll separately and only ship a linking/driving script via the asset store.







  • Arete@lemmy.worldtoTechnology@lemmy.worldGamers nexus on LTT
    link
    fedilink
    English
    arrow-up
    87
    arrow-down
    3
    ·
    edit-2
    11 months ago

    If Linus knew he wasn’t going to recommend anyone buy the waterblock no matter how it performed, but also didn’t want to show it off as a niche ‘supercar’ of waterblocks, then why agree to review it at all? Was he maybe not in the loop at all until shooting the video?

    Seems like there was no good way for this to turn out for Billet which is a real shame since they seemed to just want to show off something cool and maybe get some publicity for their startup.

    And auctioning off their handmade prototype, even accidentally and for charity, is a collosal fuck up that really can’t be solved with money alone.




  • This is interesting. Naively I’d expect that each number in a shuffled array of length n has a 1/n chance of ending up in the correct position, so there ought to be on average 1 correctly placed number regardless of the array length. I might be neglecting a correlation here, where each incorrectly placed number decreases the odds for the remaining numbers. Assuming the above though, the whole problem becomes recursive, since we’d be left with an unsorted array of length n-1 on average. The expected number of sorts would then just be n. For the time complexity, we’d have O(n) for the original shuffle, plus O(n-1) for the next, and so on, yielding O(n^2) overall.


  • Adding this option to the 3 dot menu under each post in the feed would be ideal for me. I don’t want to have to open a community just to block it, especially for the myriad niche fetish stuff that somehow make it into hot.

    Also instance-level blocking, while not yet a Lemmy feature, could be implemented purely within wefwef as a post-filtering step using a locally stored list of instance names. This could be a killer feature to differentiate wefwef from other apps. The first app to let me block every single fansocial sports team community in one fell swoop will be my go-to forever.