ckozlowski

As the spouse of an illustrator, I applaud the author for hiring an actual artist. We've seethed at the way artists work was scraped online for the training of these models, recreating their very style for the creation of these infringement engines.

The finished product benefited greatly. There's nothing quite like working with a genuine expert who knows the rules and tradeoffs on things like competition, color, etc. Author did good on providing the illustrator with a detailed brief. When the illustrator takes those guidelines and applies their style and training to the product, magic happens.

Thanks!

"setec astronomy...No more secrets."

I wrote this in another reply here, but from this article and others I've read on Space X's/Tesla's datacenters, it's the use of turbine generators that cause that enormous whine sound. (Note how similar it is to a jet engine.) I live in Ashburn, where we have datacenters all over the place. But none of them sound like this. At worst, we get a dull hum, much lower in volume, if the air handlers are working especially hard. But you need to be on top of them to hear that.

Ashburn has the infrastructure however. From what I'm reading, other places don't. So they bring in power on-site, and it seems to be much less regulated.

It likely didn't have the power requirements either. I'm just guessing here, but that sounds a lot like turbine whine. (I've heard them elsewhere, not to mention been around plenty of aircraft) My guess is that they brought one on site like they've done to other facilities to provide on-site power where the local grid isn't sufficient.

The pledge by their CEO to shut down crypto-mining equiptment feels like a deflection to me, because I don't think that's the source of the noise. It's the turbine generator, and switching to AI I don't think will change the power requirements any. We'll see I suppose.

Well, that and, by passing additional legislation.

There's two parts to this. The first is that in most cases, the issues stem from lack of clarity in existing legislation, or contradictions thereof. At anytime, if Congress does not like the way the Supreme Court ruled, they can pass different legislation.

The second stems in part from the first. If what Congress passed is interpreted as being unconstitutional by the Supreme Court, the States can amend the constitution.

There is no case where the Supreme Court can (in principle) simply make their own rules*

The debate and controversy comes where the Supreme Court is seen as making their own rules (or arguably asked to) because the legislative process is deemed too cumbersome or disadvantageous to a party. In my opinion, this is where a lot of the difficulties lie, in that the Supreme Court is asked to rule on matters that really should be more clearly legislated. But the issues are seen as easier/quicker to address by convincing 9 justices rather than two legislative bodies and a chief executive. Naturally, this brings it's own consequences.

Oh, I feel this. As a pre-teen, I loved it. SETI@Home running on our family's Pentium 100, X-Files, and hanging out on the "Parascope" forum and chatroom on AOL for all things UFO related. An "I Want To Believe" poster on my wall.

I've (thankfully) moved on past that, but I look back at that with nostalgia.

They saw a huge uptick in users during the COVID pandemic. As the corona virus is a protein shell, and their software folds protein molecules, they were able to apply it to look for targets for other molecules to attach to the virus where it would normally latch onto a cell, this could then lead to treatments.

They'd found some promising results, and were working with a pharmaceutical company to manufacture the first compounds that could then be tested. Unfortunately that company's facility was located in eastern Ukraine. =(

But that aside, they've still been going strong.

I agree, and the "not the first time" I think is key there. Setting expectations I think is crucial. For ours (5yo), we're clear about what he can watch and for how long. We control the device. "Two episodes before dinner" or so. Over time, he learns how this works. And we're not afraid to tell him that now isn't a good time for the TV.

It's not to say we never have any complaints over this, but when we do, it's rare and usually because something else is amiss (hungry, frazzled, tired).

But most instances it's like last night, where we were clear that we had time for two episodes of Tumble Leaf before dinner. At the end of the second one he announced "last one!" and got up off the couch as we picked up the remote.

5yo parent here. Agreed. And sometimes they just need to chill.

I agree with the overall sentiment. Too much screen time is bad. Kids need to get out and play, indoors or out. In our house, it's a lot of biking and playing with friends outside, Legos, Brio, Magnatiles, matchbox cars, or just crafts.

But sometimes they're frazzled, out of sorts, and would benefit from just being able to sit and chill.

So we'll put on something for him that we're comfortable with. Tumble Leaf, Blaze & The Monster Machines, Trash Truck, or the occasional Ghibli movie.

We do not give him a tablet or other portable device. He sits and watches on the couch, we set a expectation, and stick to that.

I think controlling the device is important. Keeping the screen as something we control and not something he carries around seems to allow us better control and helps him understand the limits in play. 90% of the time, we have no fuss.

And it's not bad. In moderation, TV can be just fine. Often it genuinely helps him soothe and relax (Especially if he's been really active and engaged all day), and as you said, helps us get something done. Two episodes of one of his favorite shows is great to help him unwind while we're making dinner.

But we keep time/episode limits as well, and that seems to keep things in balance along with the aforementioned things.

Thanks for looking up the numbers!

That would be quite the "budget" SMP build. The 366MHz "Mendocino" was based on the prior Pentium II core I believe. So quite the disparity in single-threaded workloads.