• 0 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle


  • Maybe not. But that was before he was president for four years - fuck, it’s still crazy to think that happened - and really forced people to acknowledge that yeah, he is a pathological liar who doesn’t give a shit about the country.

    A lot of people still suck on the tit. But a lot of others recognise that the hot pain comes from getting burned.

    You had all the tea party nutters for years - but none of them became president.


  • If I were a democrat pol, I’d want to keep Gaetz, and Trump, and all the nut jobs.

    They are loved by their base and horrible to work with in the houses, but they are electorally toxic.

    Prediction for your next presidential election: Trump will still be on trial on federal charges, he will be the nominee anyway, and he will lose badly. DeSantis will bite chunks out of him. Bullish on popcorn.

    Or Trump bites chunks out of whoever they do nominate. The party either gets moderate votes, or Trump votes, or DeSantis votes, but not all three.














  • glue_snorter@lemmy.sdfeu.orgtoAsklemmy@lemmy.mlBypassing "wifi pausing"
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    1 year ago

    Racial origins of those terms? Citation needed.

    Black and white, in the sense of good and evil, have had their connotations for a fucking long time, whereas black and white to describe skin colour are relatively recent etymologies. I’m pretty sure that Romans didn’t call themselves “white” or others “black”, for example.

    I’m willing to be taught, but this sounds like bullshit to me.

    The etymology being wrong doesn’t mean that we shouldn’t drop freighted terminology, I just don’t want false justification. Bullshit is never a valid reason to do something.


  • Pure FUD. Worse, it’s wilfully stupid.

    Are you in the habit of picking pipeline commands at random? Do you not usually have a purpose in mind? OBVIOUSLY the receiving end has to understand what it’s receiving, or what the fuck are you even doing?

    Do you believe that your text processing commands don’t have to understand what they receive?

    Let’s get the ports of the node container.

    Bash:

    docker ps | grep node | cut -n 6 -f ' '
    

    Pwsh:

    docker-ps | where name -eq 'node' | select ports
    

    First the grep command shits the bed because at some point you started a new container running a nodejs image.

    Then the cut command fails because you had a container with a space in the name, so it outputs mounts instead of ports.

    That’s a non-issue with sematic tools. Semantic tools are also legible. Yeah, I can figure out what that awk command does, but it’s meaningless unless I also know the shape of the data is supposed to operate on.

    You don’t write “USE 2nd DATABASE; SELECT 3rd COLUMN FROM 10th ROW”, do you? Why would you want to do that in a shell?