• 0 Posts
  • 58 Comments
Joined 11 months ago
cake
Cake day: November 26th, 2023

help-circle

  • We embedded third party auditors in that crypto exchange so I’m curious exactly how inscrutable tiktok really are.

    I mean the accusations are that they’re too beyond oversight and we can’t confidently audit the data, so giving us a button to stop them when we can’t see what they’re doing would be a joke. But I’m skeptical that it’s as difficult to lock down their data as we make it seem.



  • I wonder if influencers are real. People will make decisions and then gravitate towards something, and others will end up thinking that that something is the cause. But I’ve never seen evidence that an influencer with 1 million followers is anything other than a mustering ground for people already wanting to act out. I guess “influencer” is just shorthand for “we don’t actually know what’s influencing all these people, but we know where they’ve assembled!”



  • It’s new to me, I think it’s saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.

    It’s atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.

    It’s immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.

    It’s like the concept of flatpaks + structured system defining + modern common sense OS operations?




  • You use lifetimes to annotate parameters and return values in order to tell the compiler about how long things must last for your function to be valid. You can link a specific input with the output, or explicitly separate them. If you don’t give lifetimes the language uses some basic rules to do it for you. If it can’t, eg it’s ambiguous, then it’s a compile error and you need to do it manually.

    It’s one of the harder concepts of rust to explain succinctly. But imagine you had a function that took strA and strB, used strB to find a subsection of strA, and then return a slice of strA. That slice is tied to strA. You would use 'a annotation for strA and the return value, and 'b for strB.

    Rust compiler will detect the lifetime being shorter than expected.


    Also, ownership semantics. Think c++ move semantics. Only one person is left with a good value, the previous owners just have garbage data they can’t use anymore. If you created a thing on the heap and then gave it away, you wouldn’t have it anymore to free at the end. If you want to have “multiple owners” then you need ref counting and such, which also stops this problem of premature freeing.


    Edit: one more thing: reference rules. You can have many read-only references to a thing, or one mutable reference. Unless you’re doing crazy things, the compiler simply won’t let you have references to a thing, and then via one of those references free that thing, thereby invalidating the other references.




  • Reading the report makes me feel like I’m from a different planet.

    It clearly spells out Israel blocking aid to Gaza. It describes what we all would call blocking aid. If someone did what Israel does, to you, you would call it blocking. Israel blocks aid and the report makes it plain.

    Just because they have a different definition of “blocking aid” doesn’t mean the report cleared Israel. I don’t get it. Can you really just say whatever you want, end it with “but it’s not what it sounds like” and that’s the takeaway everyone gets?

    It’s one thing for a document to have arbitrary restrictions on what it can say. That happens. It’s another for people to take it so literally.

    Edit: I don’t even know what definitions they were working with, I just got a “it’s not technically…” vibe. But I do know that the report describes blocking aid.



  • mhague@lemmy.worldtoProgrammer Humor@lemmy.mlThanks ...
    link
    fedilink
    arrow-up
    4
    arrow-down
    20
    ·
    5 months ago

    I don’t see a negative. It’s foss so you ought to be relaxed about others using your code. The issues are probably just articulating problems that were already there. If it’s stuff you don’t care about… it’s a foss repository so you just ignore it.