Unfortunately the lifetime of the plutonium RTG is very very predictable (due to the half life of the isotope they use). They are constantly shutting down parts of the probe exactly because the RTG is providing less and less power, and at some point it won't even be enough to heat the probe and run the computers.
Around 2030–2036, the power will likely drop below the level needed to run even a single instrument. At that point, Voyager 1 will officially "die" as a scientific mission.
But Voyager will keep going forever.
Because there is no air resistance or friction in the vacuum of space, Voyager 1 doesn't need "fuel" to keep moving. According to Newton’s First Law of Motion, an object in motion stays in motion unless acted upon by an external force. Since there's nothing out there to stop it, it will continue its journey long after its systems go dark.
In 40,000 years: It will pass within 1.7 light-years of the star AC+79 3888 in the constellation Ursa Minor.
In 300,000 years: It might pass near the star Sirius.
The Long Haul: It is expected to orbit the center of our Milky Way galaxy indefinitely, potentially for billions of years, carrying the "Golden Record" as a final message from humanity.
Fun Fact: If Voyager 1 were to hit a pebble-sized object at its current speed, it would be catastrophic. Fortunately, space is so incredibly empty that the odds of it hitting anything larger than a dust grain for the next several billion years are nearly zero
Am still keeping my hopes up, scientists will make it wake up once every 6 months and just ping home saying it’s alive. I’ll still call it very much alive, even without science equipments running.
For a more practical example, how does this work for the daughter of a colorblind person (the colorblindness gene is on the X chromosome)? Do they have four types of cones?
Yes, but it's not limited to that case - there's two common variants of the green cone that respond to different wavelengths and people with two X chromosomes can have both, improving colour identification.
This is very good! It captures the core idea that "As a contributor, you are responsible for the code you submit" that the other example doesn't cover. Perhaps a nit is that it's a little too OpenInfra policy specific. Is it fair to say it got to it's near final form mid 2025?
Signed-off-by is a chain. The second person asserts that they delegate to the first person for the parts contributed by the first, and signs off on the ones that were contributed personally.
Hypothetically in court you'd go to the last, ask "did you write this" and only if not go up.
Usually a global lock is a lock that is taken outside all others and is taken for large parts of the runtime (or even, everywhere the thread isn't waiting on a condition variable, file descriptor and the like).
Mutex::new(AppConfig::default()) might very well be a small, leaf mutex.
I use a SSG for a conference. The git repository guides me in doing exactly the same changes every year. I have pre built blocks for the various stages of organization and go through the commits for the previous year to help me understand what to do next.
The main issue is that the image needs to have a high enough resolution to be sharp at all zoom scales. Currently my images are vector graphics that I rasterize depending on the screen resolution.
The Escher Print Gallery requires even larger scales as it uses a zoom factor of 256 across the image (vs 16 for my images)
Others have solved this by either vectorizing the Print Gallery or even rebuilding the scene as 3D signed distance field that can be sampled via ray marching.[1]
The later yields the best result but I did not want to copy it.
reply