Bow tie, and also add a monocle.

Why use print! and not println!? You’ll just mess up the terminal text flow…

This is still better than the opposite tactic of sending your opponent to google it and when they don’t find anything saying that it’s because they are not trying hard enough.

Source: google it

From a certain point of view - isn’t this exactly what happened here?

I often go into a Git worktree of one of my projects and mess around a bit to try something out. If I find it’s not working, I tell git to discard the changes with git checkout . and git clean -df. What I’m saying is exactly “on second thought, don’t do anything" - while what happens in practice is that Git restores all files to their HEAD status and removes all the new files that are not already in HEAD.

Of course, the difference is that I already have all the work I want to keep under source control, so these changes I’ve discarded really were that - just changes. He, on the other hand, “was just playing with the source control option” - so these “changes” he was discarding really were all his work. But Git did not know that.

You are being excommunicated for resisting excommunication!

That’s the beauty of religion - if our gods and prophets did not materialize to contradict what we are saying in their name, that means they approve.

Downvoting in order to bring it below @whynot’s comment.

Since I doubt he is a certified member of the National Socialist Party, I’d argue the more accurate term would be “neo-Nazi”.

They are not made of straw, either.

They’ve decided who their customers are, and it’s not you

Since FF is free - isn’t that a given?

For Windows 11, it would be an ad for Hitler instead of just a picture.

You are assuming here that I know what I want. What if there is no obviously correct answer, and even in the Everett branch that generates the optimal content for the file I’ll still think it can be improved and tell it to destroy the universe?

What if there is no correct answer?

I just use this:

#!/bin/bash

keep_generating=1
while [[ $keep_generating == 1 ]]; do
    dd if=/dev/random of=$1 bs=1 count=$2 status=none
    echo Contents of $1 are:
    cat $1
    echo
    read -p "Try generating again? " -s -n1 answer
    while true; do
        case $answer in
            [Yy] )
                echo
                break
                ;;
            [Nn] )
                keep_generating=0
                break
                ;;
            *)
        esac
        read -s -n1 answer
    done
done

I vote for “OF-Model/Simp”.

That’s your solution for everything!

Just entered it, with my Google credentials, even though I’m neither a woman nor an American. If they are going to track people who read it, let’s add as much garbage data as we can (to the tracking, not to the sheet)

This is Rust. You don’t need a safe word - safe is the default. You need an unsafe word instead.

What do you mean by “improving”? This alarming warning appears because Firefox requires permissions. Let us look at the permissions listed there:

1. “User device access”. From the docs, I’d say the browser needs it for rendering?
2. “Download folder read/write access”. This one is obvious - the files you download with your browser go there.
3. “Can access some specific files”. This one, I’ll admit, is a bit cryptic - what files does it need to access? But this one is on Flatpak for making the permission so general.

App permissions should not be about “this app cannot be trusted because it asks for scary scary permissions”. They should be about “take a look at the list of permissions the app requests and determine whether or not it make sense for such an app to need such permissions”.

Nearly every app should have a warning

No. If you put a warning on every app (except for the most trivial ones that don’t actually do anything useful) then the warnings mean nothing. The become something more than ass-covering legal(ish) BS.