Also how is "enter" less convenient than literally any other command that you'd still have to type and run to get up-to-date information in a command line?
5,165 karma · joined June 13, 2021
Also how is "enter" less convenient than literally any other command that you'd still have to type and run to get up-to-date information in a command line?
Python venvs are useful too if you have a shell for running the program and other shells that just happen to be within that directory.
But when they report on something, it's gone from the public view in a few weeks as the only place you could find it would be your own archive, assuming it goes back that far (and you wish to dedicate the space in your house), or a major library of which there are only a handful in the country that would maintain an indefinite archive.
Something more impactful than a report on another suspiciously "bungled" contract by a councillor would be to be able to see the other articles they've done on that person over the decades. Even if there was, say, a year-long delay in putting them in the archive, there's a difference between "Eyes passim" (doubly irritating as there's also no thematic index and hundreds of back issues you'd need to look in) and seeing the older reports in front of you.
When exercising, the tidal volumes are far higher (2-3L), and you breathe faster, so the lung air is at least twice as fresh as it was at rest, probably more, since fresh air is functionally 0% CO2, and you're moving maybe 6 times the gas volume in each direction.
Does that massive change in volume and diffusion gradient (at least at the start of a breath) means that you might be able to tolerate a higher CO2 level in the inhaled air?
https://constelisvoss.com/en-gb/pages/a-computer-can-never-b...
Source: entered "Böing" into a search engine.
Do many lifts have fancy algorithms in practice? I don't think I've ever had one go backwards to pick up a nearby floor, for example.
I suppose optimising where the lift loiters while empty is something I wouldn't really notice happening.
Arxiv does this presumably because some papers have mathematical expressions in the titles and abstracts. For example https://arxiv.org/abs/2401.04991
Also French labour laws and norms are probably frightening to union-phobic Big Tech companies.
This is just something software seems to do. There's a mature and fully-fledged industry in modifying entire workflows to fit software which is implicitly viewed as something that simply is the way it is.
Jira and SAP are some obvious big ones, almost with their own priesthoods, but at all levels, "capabilities drive requirements, regardless of what the systems engineering textbooks say".
And let's not forget that the entire capital-C Content industry is completely subservient to the vagaries of "The Algorithms" that are not just considered ineffable by the supplicants, but were in fact specifically designed to be that way.
The point isn't that you shouldn't record audio at 32-bit depth (which you probably shouldn't if you expect it to bring much benefit, but that's by-the-by), it's that even if you did, and you have a 7.1 system with 8 uncompressed streams, you still won't be anywhere near the point where USB 3 cable grades will start to matter.
You're the one who asked for clarification on the footnote specifically.
This is called "sample aperture jitter". Requirements scale linearly with frequency and exponentially with bit depth.
These a calculator here:
https://www.analog.com/en/design-center/interactive-design-t...
https://www.analog.com/en/technical-articles/aperture-jitter...
Sure enough, 32 bits sampling a 96kHz signal, which is the Nyquist frequency of 192kHz sampling rate, is 0.3fs. At 24 bits, it's more like 100fs, which is much more doable, but still not easy. Which is why audio bit depths usually don't go to 32 bits, despite formats like FLAC supporting that.
The practical upshot of this and other noise sources is that higher audiophile-grade bit depths and sampling frequencies are quite likely to have at least some of those bits swamped out by noise on real hardware.
This is just getting the audio recorded. Playing it back as physical sound waves adds something between quite a bit and radically more noise to the signal, even if there's never any lossy compression.
Even a hugely overkill uncompressed 8-channel, 32 bit, 192kHz sample rate audio stream[1] is under 50 megabits/second.
Any digital cable and transceiver from USB 2 (480Mbps) or 100BASE-T Ethernet (100Mbps) onwards will handily do that, with headroom for so much forward error correction that you probably won't expect a single bit error in your lifetime.
[1]: good luck getting a clock with low enough sample aperture jitter to actually record that in the first place, it's probably under a femtosecond.
And here's an use of it from 1670, so it's not a recently-verbed noun: https://archive.org/details/nature00lucy/page/137/mode/1up?q...
The gigantic Hambach open-pit mine grows by 0.3km³ a year, so that could take it (but it can't take the Saudi million m³/day plant). By the time the mine is depleted, the resulting 18km³ pit would not be filled by our single hypothetical plant for over 300 years, assuming it won't evaporate. Which leads to:
The evaporation pools might work: they'd "only" have to be 3000 acres (12 km²) to gather the 4GW of solar power at 1kW/m² for 8 hours a day to continuously evaporate that much water daily[2]. Which is certainly large, but not completely impossible. But then there's 2 million tonnes of salt per year which will accumulate continuously over time.
[1] the largest is over a million
[2] not including water not bring a perfect absorber of solar energy or differing insolation