Switch to a Dvorak layout (with blank keycaps!) and you will have all the bases covered.
We already have an emergency messaging system called Amber Alert. Just generalize that infrastructure a bit and you're halfway there.
I once worked on a very large commercial application that was based on a home-grown I/O framework which operated on similar principles. It was a complete pain in the ass. You were constantly future-proofing your data…
Require reviews to show a substantial understanding of what the book was about? That means moderation which is always dangerous but probably better than the alternative.
The wavelengths are too large for LIGO. The wave measurements were correlated with data collected from many pulsars. https://arstechnica.com/science/2023/06/nanograv-picks-up-si...
> floats really really want to be "near 1", to keep precision. The number of significant digits is identical for (nearly) the entire range of FP values. There's no value to keeping it "near 1" for IEEE 754 floats - the…
It might be stupid, or it also might just be naive, or a shift in priorities. 100x throughput improvement might just come from caching results from earlier computations (less naive) - at the cost of 10x memory footprint…
Switch to a Dvorak layout (with blank keycaps!) and you will have all the bases covered.
We already have an emergency messaging system called Amber Alert. Just generalize that infrastructure a bit and you're halfway there.
I once worked on a very large commercial application that was based on a home-grown I/O framework which operated on similar principles. It was a complete pain in the ass. You were constantly future-proofing your data…
Require reviews to show a substantial understanding of what the book was about? That means moderation which is always dangerous but probably better than the alternative.
The wavelengths are too large for LIGO. The wave measurements were correlated with data collected from many pulsars. https://arstechnica.com/science/2023/06/nanograv-picks-up-si...
> floats really really want to be "near 1", to keep precision. The number of significant digits is identical for (nearly) the entire range of FP values. There's no value to keeping it "near 1" for IEEE 754 floats - the…
It might be stupid, or it also might just be naive, or a shift in priorities. 100x throughput improvement might just come from caching results from earlier computations (less naive) - at the cost of 10x memory footprint…