To the consumer, AI is a gimmick. Why whither what little trust customers have in you and your attempts to mitigate the privacy of people who have paid you their hard earned cash?

It's your body. Duh.

I get that the heat has to go somewhere, but there are ways to build a system that doesn't "consume" much water.

Building these kinds of systems may cost more cash up-front but the cost to the people in your state/country (which becomes a political/regulatory cost to you down the road) of using water in areas where water is scarce needs to be factored in.

You want the Harvard Architecture version of AI.

Create AI-generated "fake" movie trailers for movies entering the public domain this January 1. Just be sure the AI is only trained on public-domain materials.

Here's some previous /. coverage of Public Domain Day.

Apparently, youtube doesn't mind all the AI, just any that they might have to fend off an MPA legal attack. Meanwhile, it's beginning to be difficult to wade through the AI slop.

Part of AI revenue and brainshare gathering is from the public, doing political videos and less harmful cat videos. Perhaps if people were educated to the dangerous aspects of AI, as implemented, perhaps they could try not to contribute to pollution of humanity's knowledge-base, and the destruction of people's livelihoods.

I agree that and operating system should not hog resources.

I deal with real-world objects, in this case, a vehicle body. To create a proper CFD solver such as OpenFoam, it takes a good portion of all the people in the world who know how to do it.

Well, are you going to fund me, or not?

I do computational fluid dynamics and need a system with at least 256GB of RAM. That RAM was less than $1000, and now it's nearly $3000.

I'm not surprised that people use crypto-currencies for criminal acts, just as I'm not surprised they use US Federal Reserve Notes for the same.

As for profiting exhorbitantly by inflating the exchange rate, that sounds like the free market in action to me. Back in the day when crossing the border meant changing out your paper money, you saw the same thing with money-changers near border crossings - customers were willing to pay a less favorable rate for the convenience of not having to go to a bank.

First, I'm not a Rust programmer, but I am a programmer.

Rust's claims about memory safety read to me like "we promise we are memory-safe except where you tell me they aren't. If you use a library that is marked as unsafe, you are responsible for knowing what you are doing and what the library is doing. But in all other cases, we guarantee memory safety."

If I wanted 100% memory safety, there would be a lot of things that I either couldn't do or couldn't do efficiently enough to be worth doing. A large part of kernel-level programming is one of those things.