5,570 karma · joined October 5, 2013
That's not why Voyager's sensors are being shut down, they're being shut down because the probes no longer have the power to run them.
New Horizons didn't nearly overtake Voyager. It's currently traveling about 4 km/s slower, and as it's still closer to the Sun, it's also decelerating more.
They can't, at least not for any reasonable definition of small. As I'm writing this, NASA is listening to Voyager using the DSS-14 antenna of the Deep Space Network, a dish with a 70 meter diameter, and the signal it receives is 10^-19 Watt. That's only 15000 photons per second. Coincidentally the area of that 70 meter dish is also roughly 15000 m^2, so a small dish of 1 m^2 will catch roughly 1 photon per second. Given that the datarate is 40 bits/second, it's physically plain impossible to receive the signal with a small dish.
Voyager's security is that it's really far away and you need a big, expensive dish to talk with it.
Mostly the former, some specialized software does the latter. The lowest common denominator is called the baseline, and it differs over time and between distributions. Debian for example still supports x86-64-v1 (the original 64-bit extension to x86), but RHEL 10 will require x86-64-v3, which includes SSE4 and AVX2 support.
Not all petrol or diesel is consumed by motor vehicles that (primarily) drive on the road.
Not necessarily for reusability, but it helps significantly for rapid reusability: it eliminates the need to transport the booster from the landing site to the launch site. Given that it's 9m x 70m and weighs 270 tonnes, that's not an easy process.
Partially. They have a fixed-price contract to land humans on the Moon, and notably got that contract because they severely undercut the other bids and were the only bid that actually fit within the available budget: they bid $2.94B, while Blue Origin bid $5.99B and Dynetics $9.08B.
That 3 billion is also much less than what they're spending on the project.
The big advantage of catching it with the tower is that it'll (eventually) allow them to put another Starship on top, refuel and launch again within hours, as opposed to the weeks it currently takes for Falcon 9.
I bet SpaceX does. They've solved the big problems, now it's time to solve the small problems and make reuse a reality.
This easter egg was entirely deterministic, though.
It's also often used to make things seem better or worse than they actually are. "Thousands of dollars" sounds like it's far more than for example $2,108.
Do you have any references that elaborate on that? From an outsider perspective, the time64 transition in Debian seemed to have been relatively uncontroversial and smooth. Way better than e.g. the /usr-merge.
Nah, you still have those dependencies, they're just integrated in your interpreter. That has advantages (you're now only trusting a single source) and disadvantages (you always get all the goodies and the associated risks with that, even if you don't need them).
https://wiki.nftables.org/wiki-nftables/index.php/Matching_p...
There's some convention for which scan code to use for which physical position on a keyboard, but that's not correlated with what's actually printed on the key caps. E.g. on common QWERTY keyboards the "A" key will have scan code 4, but on AZERTY keyboards it will have scan code 20.
Games can probably get away by listening for the scan codes of the keys in the position commonly used by WASD, but it's a bit fragile, and they can't actually tell you what's printed on the keys they're listening to. The lack of consistenency is certainly annoying, though...
In the USA. Many countries in Europe have renters protection similar to that of mortgage holders.
I highly doubt that. Path traversal is one of the most optimized pieces of code in the Linux kernel, especially for commonly accessed places like /bin where everything is most likely already in the dentry cache. For the script with a shebang on the other hand it first has to read it from disk (or the page cache), then parse the path from it, and then do a path traversal anyway to find the referenced file.