Let's Encrypt's mission was to get everyone to use SSL... OK. Nice. Thank you.

But now it's "We're reducing the validity window to force you to use automation by making manual updating more frequent than people will tolerate". What the hell is so bad about manual updates?

There's a whole world of people out there who are too small to set up a nice automated system but who still should be using SSL, and this is Let's Encrypt telling us they don't really believe in their mission statement.

The population will expand at a rate supported by available resources... as the population grows, the individual's share of resources reduces and fertility and/or survival rates will drop.

It's never been a case of "oops, too many people, we all die today", it's a case of "everyone gets more and more miserable but enough people die that some will live".

That's how Nature keeps populations in check... she's not a nice lady.

If you did this in Canada, whatever you create is more or less completely and instantly public domain. You could fight over details in court, but to win you'd need to have done most of what you're using the AI to avoid doing.

This is the first I'm hearing that photons created with technology are functionally different from naturally produced photons.

Kids still end up in the dark when the days get short.

My solution is not the same. You seem to have missed the 'fixed' concept. As in 'no Daylight Saving adjustments'.

Outside workers will benefit more from dropping the adjustment ' they'd keep daylight in the middle of their work day instead of having it shifted towards evening.

The time change induces stress and literally kills people. Not changing time might make northerners depressed from lack of morning light...

You know what? We have artificial lighting and spend most of our time indoors anyway. Encourage broad spectrum home and office lighting and use UTC with a fixed local longitudinal adjustment.

Not surprising to find someone 'brave' enough to downvote that. What a hero for the white power cause!

And what a horrible piece of Lost Cause propaganda that movie is. It doesn't say much that's good about the people who made it, who bought tickets, or who continue to hold it up as an example of a 'great classic' even today.

I was not disappointed, but neither was I impressed.

They did a competent job of trotting out the nostalgia bits. I would even go so far as to say they did a better job of mixing cartoon physics with the real world than Who Framed Roger Rabbit or Space Jam. It felt like a real world movie with toons in it rather than a cartoon with real people in it.

Having said that, I had nobody to root for so it didn't engage me. The story did a poor job of making me care.

It happened when you got old and apparently didn't notice.

BTDT.

I guess it's time to RTFA, because I have only the vaguest notion of how you might do that, and zero idea how you could get anything like a tolerable framerate.

Maybe I'm missing something, but I don't believe SQL includes client data rendering. At least not any SQL implementation I've ever worked with. There's always a client that has to interpret SQL data and convert it into a rendered frame as well as send user input back to SQL as a query.

That would seem to be enough of a limitation to 'Doom on SQL' to make the total project... doomed from the start. It remains an interesting exercise in getting SQL to do the rest of it. As long as the code to do so is elegant, it doesn't really matter how Rube Goldberg it gets.

In fact, I might even be more impressed as the SQL gets more convoluted.

> Conversing with just the Ai-generated audio, "At best, they feel like talking to a phone representative or someone from tech support."

Instead of that being complimentary to the quality of the AI-driven speech, it's insulting to human phone support workers. I guess we're subhuman.

I'm not so sure the shop should be allowed to choose what agent the user employs. You wouldn't like it if they banned particular web browsers and said you had to use Chrome or Edge. The browser is the User-Agent, a program that acts on behalf of the user and shows the user the results. It might also filter those results in a way the retailer doesn't like, for example removing advertisements or popups, but that's between the user and their browser.

And what does the language matter anyway when you can now type in pseudocode into Copilot and ask it to form perfect equivalent code in any language?

Whose bright idea was it to store nuclear waste right next to an ocean coastline?