Throttling everyone equally during times of congestion is also fair in its own way. I’d be okay with that.

When limiting is required, because many people are using the same network, limiting those who have already used the most seems fair.

Your comment might cause me to do something. You’re responsible. I don’t care what the legal definitions say.

If we don’t care about legal definitions, then how do we know you didn’t cause all this?

Fortran is still a good language for some purposes I think.

And I feel the same way, C++ tries to solve the problem of having too many features by adding more features.

I’d rather believe it’s a bunny than acknowledge snails that large exist.

Epic vs Google turned out a lot different than Epic vs Apple.

Also, Epic vs Google was decided by jury.

I wouldn’t consider Julia statically-typed; am I wrong?

The question mine as well be “what is your favorite compiled language?”. There is a lot of overlap between the possible answers.

The rumored 4th and 5th games…

We’re seeing more and more that our “free market” with its “competition” doesn’t provide goods and services that most people want, which makes me wonder, why have free markets and competition?

There’s also websites hosted in countries that don’t care about US law. We can access those even without a VPN, for now…

Giving bombs to Israel without condition is a… 6 point story I think

Our bug is their status quo.

Cognitive dissonance.

For a lot of people, either they accept “this trillion dollar corporation that controls all my computers, and the programming languages I use, and my code editor, is evil”. Or they accept “this trillion dollar company does lots of good things for me and is good”.

One is easier to accept than the other.

At first I though it said “Communism is the key to efficiency in a software engineering organization”; at first I thought it said something new

Every commit lists one or more parents, possibly several parents, like 8 parents. These commits thus form a graph structure.

Branches and labels are just references to commits in this graph structure; they are commit alias, just a name that references a specific commit. Branches and tags are the same, except by convention the CLI will move branches when you commit to a branch, but tags are not moved by the CLI.

(Commits may have many names, they have their commit ID, and they may also be named by a branch or tag. Commit IDs are hashes of the contents of the commit. This ensures, cryptographically, that a commit and it’s ID can never change.)

Git never deletes a commit that is less than 90 days old. If you commit something, rest assured your work is in there somewhere, it’s just that no mortal being may be able to find it. Deleting a branch removes a reference to a commit, but the commits in the branch are still there. The GUI tools usually hide commits that are not part of a branch, but you can see them using “reflog” related commands.

Command line is a GUI, change my mind

The CEOs face the day he realizes all it takes to automate his company is a personal computer: 😃

The CEOs face the day after he realizes all it takes to automate his company is a personal computer: 🫠

Can’t people just hold it for 80 years until they die?

People were staring at you because the sound of piss entering the toilet was loud? Did they not know that’s how pissing works?