Aaaah! So that's what happened! https://m.slashdot.org/story/4...

When you write any odd number in standard English (cardinal form) the final word will be one of those five words (or a compound that contains one of them), so an "e" is unavoidable.

Clearly false: eleven


Reasoning model, much?

I assume they mean coding in the sense of categorisation. It could also have been a coding error in a bot that was deleting content, thereby deleting something they didn't intend it to delete. I doubt it was a programming error in the website itself.

I think that if the agent identified itself properly in the user agent string rather than trying to masquerade as a person, there would be less of an issue. However, it is being deliberately deceptive. Hard to make any kind of argument from that starting point.

This seems to be what Common Crawl is doing. https://commoncrawl.org/

The standard also incorporates support for NFC Digital Product Passport specifications, allowing single NFC tags embedded in products to store and transmit sustainability data throughout their lifecycle.

You've got to be shitting me! Their solution to sustainability is to embed an electronic chip into every single thing?! Man, this planet is truly fucked!

I think predictions are hard, especially about the future...

Yeah, that's much harder than predictions about the past.

Sorry, $80m. My maths was off.

From the figures in TFS it appears that only $70m of the $100m is accounted for. Where did the rest of the prize money go? Was it sequestered in basalt, perhaps?

Yes, including the environmental costs of mining and transporting said rock.

Why not use both? That way we've got some built in redundancy when one of them goes rogue. (And at this point in time, it's a coin flip as to which one it would be...)

A branch is just a reference pointing to a commit. Deleting the branch deletes the reference, not the commit. Eventually, unreferenced commits will be permanently deleted, but not immediately.

I wouldn't suggest changing that.

However, knowing that so-and-so deleted the reference to commit such-and-such at a particular time is incredibly useful, even if all you have is the hash of the now-deleted commit.

It would be even better if you were able to add commit messages to branch deletion. If someone wrote a message like "Deleting the 'sort_optimisation' branch as I've realised that this approach isn't going to work. We can't sort in place as the calling code may require the original ordering to be retained in the local reference." rather than simply disappearing the branch, that would be a useful bit of communication to the rest of the team and might save some wasted effort from someone attempting a similar misguided solution in the future.

I don't really see how you misunderstanding my point about you misunderstanding other people's points proves your point about how you know better than everyone else what they need, but whatever.

Actually, taken at face value, this study is a strong argument for multi-layered interfaces, or possibly even multiple interfaces, for a given application, with different target audiences. You can see it already in things like settings panels, where an 'advanced' mode adds a lot of extra settings that most people won't understand or be interested in, but where what we used to call 'power users' can tweak the things that matter to them. They are somewhat primitive at the moment, when they exist at all, but I'd love it if this study prompted a move in that direction. It won't. But I can dream.

If you delete a file, it's gone. Oh no, wait, we track it in the history.

Why are branches any different?