marzell

"correting" lol

There's good arguments for the case that gatherer communities actually had generally better health and far more free time than farmers and agrarian society.

Farming provided the calories necessary for a population that hunting and gathering could not support (so no going back) but required basically working all day to make it work and survive less than ideal conditions. But prior to farming people often had significant more free time.

Yeah at that point I think we'd be better off if everything was just UTC and dealt with locally

You absolutely can in many engines, for instance in Snowflake... with the small exception that in all supporting engines you actually need to use HAVING instead of WHERE in your second example (because it compares an aggregation, otherwise WHERE is fine).

You can also use "correlated column aliases" (I can't recall the proper name) i.e.

    SELECT
        id AS foo,
        foo || '_1' as foo_n,
        right(foo_n, 1) as foo_ordinal
    FROM MyTable
    WHERE foo = 1;

Again, if this isn't all part of SQL standards, the reality is that a lot of engines have semi-standard (sometimes very proprietary too) ways of handling these now common patterns. For real-world use cases, the standards are unfortunately becoming increasingly irrelevant. I think it would be better in the long term to use standards, but if they can't keep up with actual usage then they will just get ignored.

> Per the SQL standard, you can't use column aliases in WHERE clauses, because the selection (again, relational algebra) occurs before the projection.

Except this works in most major vendor SQL implementations. And they all support relation aliases in SELECT... Seems the standards have long fell behind actual implementations.

Some factors I think are involved, but I don't see mentioned - EVs produce more readily available torque in general, and also tire choice heavily factors in EV range (low rolling resistance), which has a negative impact on tread life

We make corn that isn't even considered a food, legally. We subsidize that using a lot of tax dollars, to the absurd point that we pay farmers to NOT grow corn and leave fields empty. Everyone is paying for way more corn than is needed through taxes, while people claim this keeps costs low (it's more, you are just paying it in taxes). And then we come up with excuses to use more of it, like corn syrup and ethanol. This is absolutely absurd.

Long before the richest man on earth bought Twitter to be his personal megaphone to help him prepare to become president in order to boost all his personal endeavors, the letter X has been used as a sort of contraction to replace common morphemes like "cross", "trans" etc, in places where the physical representation "x" likens to a cross or crossing of some sort, or in reference to the Greek letter Chi. Must we change our use of language to support this guy, too?

Xtian Xmas xfer tx/rx xor...

I believe the "thinking out loud" is fundamentally part of the process of "text completion" which is what it is doing. Certainly we can (and do) break things apart and add layers that could be used to effectively do this by adding more steps and processing time. But ultimately in a single turn, the entire conversation up to that point (including instructions you may have added telling it to not think out loud) is the input, and the output will reflect that.

I'm not arguing your point, but this is the general state of gaming today. A significant portion of "single player only" games require you to be online, contain "online" content, and access to the game can/will be effectively removed when servers/services go offline.

The second point, yeah that's relevant.

On the first point, just give each person n-1 shards, each missing a different one. Then any 2 can decrypt. Or configure it for however many participants there are and they minimum number needed to encrypt.

What's the practical benefit over just sharding a decryption key and handing out multiple shards to each person?

for something a bit more robust, check out DuckDB. It's a library you can embed, use it to run SQL on local files as well as connect to databases, do joins, analytics, etc.

Same. It took me years to even figure out I could just buy programming books from the store. But progs like Magenta and AOHell, plus the F1 help/documentation built into vb and the like, set me on the path.