Forgot your password?
typodupeerror

Comment Re:But the real cost is increased service prices (Score 1) 72

Nuclear reactors use most surface water, not ground water.

Datacentres are no pickier. You can even cool a datacentre with saltwater, you just need a heat exchanger.

Also, closed loop does not evaporate. The loop is not closed if stuff escapes from it.

You're arguing with the actual terminology used in the nuclear industry. "Closed loop" or "closed cycle" designs have the water pumped in a cycle through cooling towers. The towers lose water to evaporation, taking heat with them, but the rest of the water is returned to be reheated again. "Open loop" or "open cycle" designs have no cooling towers. The water is heated and just discharged hot. They consume much more water (over an order of magnitude more), but most of that is returned. Closed loop are more common, but you see open loop in some older designs, and in seawater-cooled reactors.

Comment Re:According to the summary... (Score 1) 107

I've printed many hundreds of kg on my P1S, thanks.

I do not consider having to write data out to a card and transport it back and forth between the printer and the computer to be the pinnacle of convenience. That's something that would be considered embarrassingly inconvenient for a 1980s printer, let alone a modern net-connected device. And it's designed to be inconvenient for non-cloud prints for a reason.

Comment Re:But the real cost is increased service prices (Score 1) 72

Also, anything sounds big when you put it in gallons. Doesn't sound so big when you mention that's 92 acre feet, the amount used by less than 20 acres / 8 hectares of alfalfa per year. Or when you mention that a typical *closed loop* 1GW nuclear reactor uses 6-20 billion gallons of cooling water per year (once-through uses 200-500 billion gallons, though most of that is returned, whereas closed loop evaporates it)

Comment Re:That makes sense. (Score 4, Interesting) 81

I don't think it has anything to do with that. As soon as I saw the headline, my mind went "cohort study". And sure enough, yeah, it's a cohort study. Remember that big thing about how wine improves your health, and then it turned out to just be that people who drink wine tend to be wealthier and thus have better health outcomes? And also, the "sick quitter" effect, where people who are in worse health would tend to stop drinking, so you ended up with extra sick people in the non-wine group? Same sort of thing. This study says they're controlling for a wide range of factors, but I'd put money on it just being the same sort of spurious correlations.

Comment Re: Pare down the bloat (Score 1) 91

This there decision needs to reflect the actual support costs. Right now x86-64v2 is probably the least common denominator in terms of not requiring a lot of special hoops to support. Maybe you could argue x86-64v1 stuff is still viable but I'd counter you have a lot of instruction set inconsistency there in those products and from a performance and efficiency perspective it probably does not make sense to be using them as daily drivers of contemporary software.

Wouldn't v2 be backwards compatible w/ v1, the way CPUs are designed? What exactly would have been introduced into v2 that would have broken v1 compatibility to the point that one would need separate codebases for each? I can understand the 32-bit vs 64-bit argument, but not this

Comment Re:Pare down the bloat (Score 1) 91

Surely, the kernel could benefit from a concerted effort to pare down support for devices that are 30+ years past their prime and focus more on chasing bugs?

I can certainly understand ending support for 32-bit CPUs if 64-bit is now the norm

However, I don't get why beyond that, older CPUs have to be abandoned. I know that's not what was mentioned in this article, but if AMD introduced the Athlon-64 and the Opteron-64, I don't see why support for them needs to drop, since they use the same instruction set as today's Ryzens, sans whatever AMD may have introduced since. Since it's a subset, it can be a common base, and anything specific to newer CPUs can be added. If a CPU doesn't have the newer extensions, then supporting it w/ the subset of today's feature set shouldn't be an issue

Comment Re:Stop purchasing Bambu products (Score 2) 107

They've made a nice easy-to-use ecosystem. For $400 you can get a P1S that supports adding an AMS, auto bed leveling, enclosed-chamber printing, high precision, high print speeds, and 300/100C nozzle/plate temps, and has an easy cloud print service and a robust ecosystem of models you can just download and print with no extra config straight from the app.

But yeah, their behavior is increasingly entering bad-actor territory. I wonder how long it'll be before they lock entry-level printers into their branded filament?

Slashdot Top Deals

Debug is human, de-fix divine.

Working...