Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment What is the fin behind the main sail? (Score 1) 10

Manned sailboats don't have such fins, but they have canvas sails. Perhaps the fin helps with the aerodynamics of a rigid sail?

I would also like to know how they handle special sailing situations. How do they handle very high winds? Can they move the sail out of the way somehow? For example, move a weight up inside the sail and turn the boat 90 degrees to its side, or upside down)? How would they avoid running aground when they are near land and there is no wind? Can they drop anchor? Do they have a propeller?

Comment Re:Indirect is unfair (Score 1) 40

Well do they? Do the energy providers build new power plants without increasing emissions? Apparently not, or else we wouldn't be having this discussion.

Home builders in California are required to build solar roofs on new houses. Why should houses be required to build their own solar power plants but data centers get off the hook?

I don't care who builds the renewable power plants, as long as they get built. But the U.S. government doesn't think that emissions are a problem, so it won't even look for a solution.

Comment Re:Indirect is unfair (Score 1) 40

Now let's do a thought experiment. I make a contract with an energy company when they use 100% solar. Next year they change business plans and go to 50% nuclear and 50% coal. Why am I responsible for their decision to produce CO2 and create radioactive waste?

You should not be responsible for any emission changes after you make the contract. Also the original article should take into account the increase in electricity consumption, not for changes in the emissions per kWh.

But when you make the contract, you should build the renewable energy power plant to provide this power (or pay someone else to build it). Regulatory authorities should monitor that these power plants get built and used.

It's very simple: Data centers should be built together with renewable power plants to power them.

Comment Re:Indirect is unfair (Score 1) 40

First of all, the "indirect emissions" term is misleading. Obviously tech companies mostly consume electricity, and all purchased electricity is classified as indirect emissions (as opposed to electricity from backup generators that the companies own).

But yes, indirect emissions is fair. You can't blame electricity companies for the emissions caused by the additional electricity you buy from them, just like we can't blame only fossil fuel companies for the fossil fuels that we consume.

All consumers of energy should be forced to pay for clean electricity generation of every additional power that they add to the system. That would be fair. If you build a 1 kW house, pay for 1 kW of new wind/solar. If you build a 1GW data center, pay for 1 GW of new renewable energy power plants. Basically, don't increase your "indirect emissions".

Comment Re:Which is it? (Score 2) 80

And more importantly, how long at what heat (gas or electric oven) for the meatball to be well done?

Each person radiates 100W of heat (2000 calories per day), so according to my calculations, the sphere of all people would radiate 261 kW/m2. Let's bring this down to the dimensions of a toaster oven, roughly 20x20 cm, then the radiation is about 10 kW per toaster-oven, which is plenty to cook the surface.

But this is the steady state solution, which might take a long time to reach (days, months, years?). In the meantime the people would be dead and stop radiating heat. So I don't think the people would self-cook. Conversely, if you heat the surface with such power, it might take a similarly long time (days, months, years?) for the whole sphere to cook, while the surface would be incinerated. Don't do this folks... We don't have the technology yet to cook such a large meatball.

Comment Re:LOL Too Late (Score 1) 31

Humans will move to the underground internet, visiting only domains that they exchange hand-to-hand, interacting only with users they meet in person. Registration will be by personal invitation only. If you see a site with open registration, stay away. It is planted by the enemy. Slashdot registration will be reworded: New human registration is now approved by humans. Please come to the park between sunset and sunrise, so we can take a blood sample, to prove that you are human. The problem is, in a few years, humanoid robots will come to the park, with human skin and blood, terminators. What will we do then?

Comment Re:Let me quote many C and C++ programmers ... (Score 1) 116

Thank you for correcting me. Indeed C++ cleans up intermediate values in expressions. It seems that it is even easier to overload operators in C++ than in Rust, because you don't need to overload different variants of the operator for references and values. One overload handles both original and intermediate operands.

Comment Re: Let me quote many C and C++ programmers ... (Score 1) 116

The & symbol in Rust is not a "dereferenced pointer." &a + &b is not pointer arithmetic. &a means that you use "a" by read-only reference (without copying it or modifying it). Therefore, it makes perfect sense to use it for arithmetic, even though it looks a bit strange. The operation will use the existing values without copying them or modifying them, and produce a new value. There is a complication, that the result of the computation is a value, not a reference, so to cover all situations you need to define the arithmetic operators for all combinations of reference + value, i.e. 4 overloads for each operation. Luckily, you can create Rust macros to generate the extra 3 overloads from the first one. You don't need to use "&" for primitive types like f64, because such types can be implicitly copied as needed. Rust defines the arithmetic operators for both f64 and &f64. I think this is the right approach for all types. Once the intermediate value is used in another operation (function call), it is "owned" by the new operation, which means that it is automatically deallocated when the operation returns, unless the operator returns it, in which case its ownership returns back to the caller. The result of an arithmetic expression is a single value, with all intermediate values cleaned-up (deallocated).

Whether or not there are pointers involved is irrelevant. With Rust, I think in terms of references, not in terms of pointers, unlike languages like C++, Java and Go which use pointers much more extensively. A pointer in Rust is usually hidden in a standard library type, like Vec or Box.

Rust has built on the experience provided by 20 years of C++, Java, and other languages. Statements like "Rust is still just a toy" and "entirely not proven" dismiss all this experience. Every good language should be a toy that programmers like playing with. You learn it by playing with it. The Rust compiler does a lot more work than other compilers, even giving suggestions about how to fix syntax/usage errors, so it becomes your tutor.

Comment Re:Let me quote many C and C++ programmers ... (Score 1) 116

I doubt that C and C++ programmers quote the same things, and I bet most C and linux programmers could easily substitute "Rust" with "C++" in your quotes, except for the last two:

"Rust is still just a toy, entirely not proven, it will be decades before it is trusted."

"Rust is still very much in beta, and not really used in production."

C++ is a toy used in production, producing decades worth of defective code, it will never be trusted.

After 3 months of learning Rust, my impression is that Rust's beta is much better than C++'s maturity. Take operator overloading as an example, for types like polynomials that use heap allocation. Rust does this correctly, so in the expression &A + &B + &C, the result of (&A + &B) will be automatically deallocated after it is added with &C. Can this be done with C++? I tried decades ago and gave up.

Comment Re:has anyone calculated cooling impacts? (Score 1) 76

Social warfare applications like the one you mentioned, where millisecond latency makes a difference between life and death, is not the only supercomputing use case. A lot of scientific computing and AGI itself will not be judged by whether you return an answer in 100 ms, but by whether you return a correct answer, reasonably fast. A lot of computing data is already produced in space from weather satellites, imaging satellites, space telescopes, etc. For starters, space data centers could crunch through that data. Cooling stuff in space is easy. The James-Webb telescope is kept at 50K just by keeping it in the shade (from the sun, the earth, and the moon).

Slashdot Top Deals

"It's like deja vu all over again." -- Yogi Berra

Working...