If you had any critical thinking skills, you'd realize that my original point applies not only to keeling over, but also to feeling unwell.

More feeble people would suffer throughout the year with either permanent DST or standard time than the current one bad night in March. (Which, BTW, could be totally avoided by planning ahead and adjusting your bedtime a few minutes per day in the preceding week.)

Biology matches DST adjustments more than a fixed clock. Most everyone woke up with the sun from the dawn of humanity until the late 19th century, and adjusting the clock for the seasons stays closer to that.

Then I suggest you never travel east or west by more than a few miles. You seem feeble.

You know what's aligned even more with circadian biology?

Keep the current system, get up off your ass, and change your clocks twice per year without whinging like a precious snowflake.

That way you you don't have to deal either with the sun beating down on you while you try to sleep at 4am or with your poor children getting run over in the dark on their way to school.

Sure, a couple of codgers might keel over in march, but they were probably gonna die soon anyway. It's much harder to measure the statistics of all the other people who would die steadily throughout the year due to the aforementioned issues, as well as similar problems caused by a static clock that doesn't adjust at all to when the sun actually rises. However, I would bet good money that it would add up to far more casualties overall.

For some reason, I seem to be in a small minority on this issue, though. It's probably because everybody would rather believe in a solution to the problems of living on a tilted axis that's clear, simple, and wrong.

People don't read a lot of things that they agree to, especially if it's 20,000 words in a postage stamp-sized text box on the new toy they just turned on. However, anybody who's not an idiot realizes that most everything in an agreement that they haven't read is against their interests, and plans accordingly. I personally always look for binding arbitration agreements and make sure to opt out of those whenever possible.

Oddly enough, the Anthropic TOS and privacy policy actually aren't all that obtuse and can be skimmed in a few minutes. They make it clear that they'll be looking for problems with what you upload and what kinds of problems those might be. Like I said, you can easily avoid all that by using a paper notebook for your diary.

If you look at Anthropic's terms of service and privacy policy, it clearly states that they can look at your content in order to enforce their usage policy. You have to agree to this when you set up an account or use their service. Given that this is an AI company, you can bet your content will be screened for violations more efficiently than if humans were involved at every step.

If she really didn't mean for anyone else to view it, she would have scribbled it down in a notebook instead of uploading into a cloud owned and policed by strangers and their robots.

It's a paper copy of underground utility records and a backhoe.

Probably the next code that it outputs will be:

My Walmart is worse than that. They didn't have any price tags at all. Just video screens with AI avatars of a guy in baggy pants sitting cross-legged on a rug.

When I walk by, he says "Look at my cotton swabs! I offer you the best cotton swabs in the land!"

I say: "Well, how much to they cost?"

He squints at me, looks me up and down for a long while, then says: "For you........ I give to you seven hundred and fifty swabs for two pieces of silver only. Believe me when I say you will search this entire kingdom and not find a better deal!"

The conversation only seems unnatural because they didn't use the right avatar.

If you choose the "Max Headroom" avatar, then everything will look and feel exactly as you would expect. Moreover, the dystopian vibe he gives off will be a perfect fit with the current state of the world.

Wrong again.

Moreover, many of the big complex systems I've worked on were big and complex mainly because OOP nitwits had designed them. They often didn't understand how computers actually work, lost sight of the fact that they were writing a computer program, and spewed out frameworks that filled countless gigabytes of resident memory with endlessly deep layers of nothingburger abstractions. Maybe that didn't matter so much when memory was cheap, but that's no longer the case.

If you think that there's only one way to deal with large data sets, you're a just noob that needs more experience before spouting your theories.

C++ is just as much of a sieve as C, only more obtuse.

"Object models" are an anti-feature.

The ideal for memory safety is to have an air-tight pressure vessel.

With C, you're starting that task with a colander. You've managed to fill two of the colander's holes with silicone caulk. Congratulations.

A space weapons arms race plus one million data center satellites.

What could possibly go wrong?

And fission plants definitely aren't cheap.

Especially if you include the unsolved issues such as waste barrels stranded on the beach.

"But but no true Scotsman would put barrels..."

Just shut up.