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

help-circle
  • I don’t see how what conservatives say has to do with reality.

    Biden has been “senile” and “too old” for years now, during which time we’ve had a functioning Biden administration.

    The Trump admin was limp, chronically understaffed, weak, ineffectual. That’s what they’re pretending is better than Biden. Conservatives don’t even care about senility so if you hear them rag on Biden and think they’re right, you’re not understanding what they’re really saying.







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


  • Consider their law strategy: instead of targeting bad behavior, they target people they don’t like.

    He might not be able to understand a word being bad because of the actions ascribed to it. “So if Bernie did those things you’d call him a fascist?” “Uh yes, that’s not a gotcha.”

    He’s more likely to think something like “fascism isn’t actually a bad word because it just means conservatives and that’s my team”


  • mhague@lemmy.worldtoPolitical Memes@lemmy.worldC'mon Joe!
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    25 days ago

    “Both sides” is not discussion or criticism, it’s a fallacy.

    I’m excising the fallacy.

    What team do you think I’m on exactly? I don’t think people should shit on Trump by calling him fat. I’m conservative. I don’t think Democrats are as bad as Republicans. I’m liberal. I think geopolitics is a hard game to play. I’m Kissinger.

    Or maybe I’m just someone who doesn’t do tribalism to the same degree? Maybe I’m a one man sports team?



  • mhague@lemmy.worldtoPolitical Memes@lemmy.worldC'mon Joe!
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    25 days ago

    I don’t get it. Two people stand in the same spot. But they took different routes to get there and they have different destinations. They even stand differently. They don’t talk the same, they don’t dress the same, and in fact one of them looks like they will rob you.

    But I guess if the entire point was “Look. Two people stood in the same spot.” then… yes. It’s not a useful observation but it’s technically correct.





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