The git commit history, perchance?

We can, and likely will. The headline is poorly worded and misleading - de rigueur for Slashdot unfortunately.

This sort of thing just happens sometimes.

But I will be curious to see how this plays out, given the Russians have already gone back and forth regarding whether they're going to stick with the ISS to the end of its operational life. They might decide the decision's been made for them.

Daughter of Julie Hotdog and Andrew Hoagie.

"Hey Kiro, I'm finding that you really suck at generating code. Please rewrite your internal codebase so you suck less."

It's Australia, so maybe they'll just all go walkabout.

I work at a university. Even old me is aware that Discord is used quite a bit by our students. Good luck regulating THAT.

Okay Boomer.

Cumberbatch also portrayed Smaug and Sauron in The Hobbit films (2012-2014), Khan in Star Trek Into Darkness (2013), and Dr. Strange in six Marvel movies.

Yeah, let's not mention the role that made him famous - Sherlock Holmes in Sherlock, which was pretty darn good for the first couple of seasons (before it fell off a cliff).

Claude is much better for coding.

He's probably like one of those people who knows that Africa has been fucked over by other nations as long as there have been other nations to fuck them over. Everyone's had a turn abusing Africa.

Your first full paragraph is 100% opinion. Run along now.

I saw that line in TFS and thought "what are we, 10 years old?"

As far as the arguments against hyperloop goes - we've hashed those out ad nauseum before. The only thing that's keeping the hyperloop hype train going is that, somehow, there are still a few Musk fanbois in existence.

It's easy to have unique keys in your spreadsheet so that you can easily relate information on different sheets to one another. The problem is, actually doing the processing that a SQL server would do trivially is irritating, and then it will be processed slowly every time. Whatever Excel does or doesn't cache, it isn't enough. You can do big complicated things, but they work slowly, and maintaining it is irritating at best. When you do complicated things either your formulas get long, or you wind up having to write code, or in fact often it's both. At that point you're way better off IMO doing it in something else so that at least performance is good when you're done, and you never have to screw with editing a long formula.

That's exactly why it should be in a database and not a spreadsheet. Spreadsheets are best when you have a reasonably limited number of columns. It's also a horrible PITA to use them as a relational database (it's more or less possible, but you don't want to do it) so hiding pieces of that complexity in other sheets in order to limit the data the user interfaces with on the main sheet is just a lot of extra work you wouldn't have to do if you used another solution.

It doesn't really matter where it fails, if Excel can do it and Sheets can't then Google has to admit inferiority to Microsoft which is never a good look.