One alternative would be to make diamonds out of the extracted carbon and drop them to the ground. The released oxygen could then bind to crustal aluminum, iron, silicon, calcium, etc.
Venus has sadly little hydrogen, so you won't get oceans.
396 karma · joined October 16, 2022
One alternative would be to make diamonds out of the extracted carbon and drop them to the ground. The released oxygen could then bind to crustal aluminum, iron, silicon, calcium, etc.
Venus has sadly little hydrogen, so you won't get oceans.
As your balloon drifts up or down through it, the sheen of moisture it collects on its surface is maximum strength sulfuric acid. I hope your balloon is not of a material subject to oxidation, because if it is, you will soon discover a place even worse than in that cloud.
Probably you could speed up the build by consolidating it into a few files; linking is about the slowest thing compilers do, although mold could help, there.
Moving small things into headers might seem like it would slow down the build, but anything wholly defined in a header doesn't need to be linked.
Looking at your pull 256, a delegating constructor would seem to be right thing, but initializing in the class declaration is absolutely best. I wonder who still wants it pre-C++11.
https://www.gab-neumann.com/Corrosion-resistance-of-impervio...
Asteroid material will become important once orbital construction has seriously taken off, after Musk is long dead. In the meantime, the only valuable exports will be the engines that got supplies out there. With their bells cut off.
I would bet any amount of money none will.
Getting 250 tons of high-strength steel cable (sheathed against corrosion) to Venus is left as an exercise for the reader. Likewise, a big enough balloon to hold that up. And a strong enough winch.
But in practice, you would make the cable of carbon extracted from atmospheric CO2, instead, and it could support itself all the way down to the surface, 50 mi below. You would need to protect the end against acid vapor corrosion at 470 C: another exercise for the reader.
Edit: maybe not fine. Resistance to H2SO4 corrosion falls off sharply as its concentration approaches 100%. On Venus, the clouds would be very nearly 100%.
Numerous materials can be extracted from the outside air, including oxygen, hydrogen, carbon, sulfur, nitrogen, and even some metals.
A day/night cycle is about 100 hours, depending on how close you are to a pole.
A nuclear reactor is as simple as a big fabric tube suspended vertically with a naked atomic pile hanging near the bottom, and a wind turbine turning in an opening at the top, the only moving part.
You need something non-solar because nights are long.
Alternatively, you can store energy with a weight on a cable attached to a generator. Play it out to discharge, winch it back up to charge.
Or maybe different layers of atmosphere circulate at different rates. If so, you can hang a wind turbine in the next layer below.
Ore on Earth is worth a lot more, and is right here, ready to be dug up.
But the topic here is type systems, and Rust's is more like C++'s than any other, and vice versa. C++ compilers used to have error messages that were hard to interpret, but competition between compilers has improved them.
Meanwhile, C++ itself has changed enabling better error messages because it is clearer what your code is trying to do.
At issue here is only how much parsing is allowed.
I.e., desalination by itself would be fine, except CC has enough water for its own use without. I suspect the tricky swap was meant as a way for Exxon to avoid getting blocked trying to do desalination on its own.
It says "Though there are likely millions of stellar-mass black holes roaming the Milky Way..." I thought it was billions, now.
500 ly is supposed to be equivalent range for a magnetar quake. I think the nearest known magnetar is around 10x that. But even 1% of the radiation needed to sterilize the solar system would be pretty uncomfortable.
Maybe start by shifting the orbit of the whole solar system out-of-plane. (I guess that would be done by electromagnetically stimulating the sun to produce a polar jet for a few million years.) That provides our distant descendants another 100M years to alter the orbit further so as not to just plunge back in on the other side. But even without, the risk would grow back to our present level for only (say) 10M out of each 100M years, strictly an improvement.
Orbital plane maneuvers are infamously expensive in delta-V.
Spending the following 100M years increasing our galactic orbital radius might put us in the outskirts before crossing again, if we did not actually escape entirely.
We might also be able to put off by a few billion years the sun itself sterilizing the planet, using the same apparatus. We could only hope it would not be abused to destroy us itself.
Andromeda isn't due for another 4.5 Gy. Presumably its central black hole and ours will merge shortly thereafter, maybe sterilizing the whole galaxy? I am content to leave worrying about that to others.
I have strictly more complaints about John Markoff.
He is personally responsible for, e.g., Kevin Mitnick not being allowed to use the telephone while in prison, out of trumped up fear he could hack with it.
We are still interested in feature extraction and scene composition, which both benefit from more compact representation.
To compete with hardware-assisted decoding in display hardware, fractal rendering would probably need to be coded to run in Vulkan.
Modernizing, however many users it has would benefit immediately.
Equalizer::~Equalizer(void)
{
}
It probably could be cut to half the LOC just by modernizing, and get more reliable and faster.