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.

On the flip side, I have enjoyed the few Canadian shows that made it to the U.S. (especially during the writer's strike).

Hard to say, but rember that it was because of similar laws in Canada that we got The Great White North with Bob and Doug McKinzie.

Biden went around congress to fund a different genocide. Pretty words, but living up to them is another matter.

On the other hand, If I have an ultralight and realize I need to move over 200 people at once, I know I'd better talk to a domain expert rather than trying to tie 250 ultralights together with kite string.

Eastern Europe was screaming about how dangerous this was, but they weren't listened to.

One of the most insane things is how after Russia's surprisingly poor military performance in the Georgian war, the Merkel government was disturbed not that Russia invaded Georgia, but at the level of disarray in the Russian army, and sought a deliberate policy of improving the Russian military. They perceived Russia as a bulkwark against e.g. Islamic extremism, and as a potential strategic partner. They supported for example Rheinmetal building a modern training facility in Russia and sent trainers to work with the Russian military.

With Georgia I could understand (though adamantly disagreed) how some dismissed it as a "local conflict" because it could be spun as "Georgia attacking an innocent separatist state and Russia just keeping their alliances". But after 2014 there was no viable spin that could disguise Russia's imperial project. Yet so many kept sticking their fingers in their years going, "LA LA LA, I CAN'T HEAR YOU!" and pretending like we could keep living as we were before. It was delusional and maddening.

The EU has three times Russia's population and an order of magnitude larger of an economy. In any normal world, Russia should be terrified of angering Europe, not the other way around. But our petty differences, our shortsightedness, our adamant refusal to believe deterrence is needed, much less to pay to actually deter or even understand what that means... we set ourselves up for this.

And I say this to in no way excuse the US's behavior. The US was doing the same thing as us (distance just rendered Russia less of a US trading partner) and every single president wanted to do a "reset" of relations with Russia, which Russia repeatedly used to weaken western defenses in Europe. And it's one thing for the US to say to Europe "You need to pay more for defense" (which is unarguable), even to set realistic deadlines for getting defense spending up, but it's an entirely different thing to just come in and abandon an ally right in the middle of their deepest security crisis since World War II. It's hard to describe to Americans how betrayed most Europeans feel at America right now. The US organized and built the world order it desired (even the formation of the EU was strongly promoted by the US), and then just ripped it out from under our feet when it we're under attack.

A friend once described Europe in the past decades as having been "a kept woman" to America. And indeed, life can be comfortable as a kept woman, and both sides can benefit. America built bases all over Europe to project global power; got access to European militaries for their endeavours, got reliable European military supply chains, etc and yet remained firmly in control of NATO policy; maintained itself as the world's reserve currency; were in a position that Europe could never stop them from doing things Europeans disliked (for example, from invading Iraq); and on and on - while Europe decided that letting the US dominate was worth being able to focus on ourselves. But a kept woman has no real freedom, no real security, and your entire life can come crashing down if you cross them or they no longer want you.

(Score:X, Troll)

And yet, your imaginary friend still isn't real. ;)

They clearly didn't even use a proper image generator - that's clearly the old crappy ChatGPT-builtin image generator. It's not like it's a useful figure with a few errors - the entire thing is sheer nonsense - the more you look at it, the worse it gets. And this is Figure 1 in a *paper in Nature*. Just insane.

This problem will decrease with time (here are two infographics from Gemini 3 I made just by pasting in an entire very long thread on Bluesky and asking for infographics, with only a few minor bits of touchup). Gemini successfully condensed a really huge amount of information into infographics, and the only sorts of "errors" were things like, I didn't like the title, a character or two was slightly misshapen, etc. It's to the point that you could paste in entire papers and datasets and get actually useful graphics out, in a nearly-finished or even completely-finished state. But no matter how good the models get, you'll always *have* to look at what you generate to see if it's (A) right, and (B) actually what you wanted.

And clearly God (who as we know, is a scalar field) is an AI. That's why there's so much "slop" in the Bible - factual errors, contradictions, different versions of the same text that heavily contradict each other, etc etc. It all makes so much more sense now!

At one point last week I pasted the first ~300 words or so of the King James Bible into an AI detector. It told me that over half of it was AI generated.

And seriously, considering some of the god-awful stuff passing peer review in "respectable" journals these days, like a paper in AIP Advances that claims God is a scalar field becoming a featured article, or a paper in Nature whose Figure 1 is an unusually-crappy AI image talking about "Runctitiononal Features", "Medical Fymblal", "1 Tol Line storee", etc... at the very least, getting a second opinion from an AI before approving a paper would be wise.

The problem is that the LLM only does one trick. When you start integrating other software with it, the other software's input has to be fed in the same way as your other tokens. As the last paragraph of TFS says, "every clock check consumes space in the model's context window" and that's because it's just more data being fed in. But the model doesn't actually ever know what time it is, even for a second; the current time is just mixed into the stew and cooked with everything else. It doesn't have a concept of the current time because it doesn't have a concept of anything.

You could have a traditional system interpreting the time, and checking the LLM's output to determine whether what it said made sense. But now that system has to be complicated enough to determine that, and since the LLM is capable of so much complexity of output it can never really be reliable either. You can check the LLM with another LLM, and that's better than not checking its output at all, but the output checking is subject to the same kinds of failures as the initial processing.

So yeah, we can do that, but it won't eliminate the [class of] problem.

Every tech company needs at least three things to start with: The business guy, the brain, and the lawyer. Ideally there should also be a marketing guy, but you can add them in later. Also, none of them have to be male, I just like saying "guy", buddy.

Yes and no, depending. If you are building an application in Excel, yes, all you said is true. If you are using one, no, none of it is. Spreadsheets can be set up such that the user just stuffs data into them where they are supposed to, then clicks a button to get results. Or maybe they don't even have to hit a button.

For the simplest useful example I can think of, I put together a spreadsheet which produces a table we use for asset valuation. This spreadsheet changes every year. If you load my spreadsheet, it will be correct for the current year. No user has to think about that at all, they just load it and get a correct table. You can extrapolate this to basically any level of complexity because Excel has VBA and you can script everything. The user just follows instructions, and they aren't even allowed to edit any cells which could break anything.