The length of a noon-to-noon day (synodic day) varies from +29.9 seconds near the winter solstice to −21.3 seconds near the autumnal equinox[1]. If you account for the seasonal changes, you get closer to the ideal solar day which only deviates by milliseconds from 86400 s, but that deviation does pile up and "forces" leap seconds. I say "forces" because it's a legal requirement that the time tracks the sun.
Going to leap hours I think is a sufficient kick of the can down the road, one is only needed every few centuries. Pretty sure something'll happen in the next 600 years that obviates the need for that though (nuclear war, asteroid, technological singularity, need for a unified solar system time...), so us hack programmers can assume all three of those things.
From the bubble center plot, I'm guessing that the bubbles are separated on average about a few mm apart? Taking the other comment's guess at face value, you're going from about 2 mm to 20 um, so 2 orders of magnitude. Air (technically SF6 in the article) and water (RBC is close enough) have acoustic impedances that differ by 3.5 orders of magnitude.
My assumptions here are *extremely generous*, i.e. favorable to the "oh, we'll just make it work with natural contrast", and even then, they can't hand wave 5-6 orders of magnitude of improvement. Furthermore, because of the use of super resolution, I'm guessing there's some exponential factor in there, i.e. double the density of bubbles/tracking points past some critical limit, then you need 8x the data to reconstruct things.
Fortune links to a BBC article, which doesn't really provide any more detail about the testing conditions. I wonder if rubbing a bar of soap on your windows would reflect light and be easier to wash off. Also, were the windows tested low-E or not?
I still don't understand why programmers seemed to get off on this sort of shit. Doing `while((dest++ = src++));` is great and all (maybe fine because it's kinda idiomatic now, but should you really be using that over `strncpy`?), but being clever like that in real code makes it harder to review, and harder to understand months down the line. I've mentally cussed out 'whoever wrote this confusing shit' to only `git blame` myself.
Why would this be any different from dropping a coin or other small metal object? If you're worried about ultrasonic noise pollution, nearly every SMPS operates there, and they're constantly running.
Ever play Doom (2016)? It's about renewable energy.
Pesky little--very minor--side effect that it's extracted from Hell, and using it causes the denizens of Hell to spill over to our side. One would say they are "unleashed".
By raising the price of oil so much, our dear leader is trying his level best to accelerate the transition away from fossil fuels.
Nowadays it's about efficiency and cost-effectiveness. Sure, 99% of the time a Shahed-136 might "lose" against a Patriot, but a Patriot missile costs 200x what a Shahed does.
Laser and EWar approaches are going to be more successful long-term as the price per "shot" is dramatically less, but deployments are slow.
1. Store your money in a 0% interest account—leave RAM totally unused—or put it in an account that actually generates some interest—fill the RAM with something, anything that might be useful.
2. Store your money buried in your backyard or put it in a bank account? If you want to actually use your money, it's already loaded into the bank.
Imperfect analogies because money is fungible. In either case though, money getting spent day-to-day (e.g. the memory being used by running programs) is separate.
US healthcare is a leader in administration fees (e.g. paying health system executives) compared to other countries around the world. High US healthcare cost isn't because of increased usage, but because of the higher admin fees and higher prescription drug prices. Prices are fixed high because law prevents the government from negotiating prices (o.b.o. Medicare/aid), and those provisions were inserted on behalf of pharmaceutical companies so their executives could make more money.
Paying individual workers more may have some benefits, but I think the key issue is usually overworking and burnout because the incremental cost of adding a whole new employee is way higher than just pressuring workers to do more work in the same time.
Spotlight search is infinitely more useful than the Windows 10+ start menu. 99% of the time I'm just using it to open an app or a recent document/download.
In Windows, if I hit [Win], type "fusion" (to open Fusion 360, an app in the "Start Menu" folder, for what that's worth nowadays), there's a 70% chance it will do a Bing search for "fusion".
While "The Liberator" (one of the first 3d printed guns) was interesting as a test of the technology and what it means for the law, I don't know if I'd trust using one to not blow up in my hands. Pretty sure you could assemble a zip gun in a Home Depot (they even sell cartridges for powder-actuated tools) that's less dangerous for you, more dangerous downrange.
It is a total mystery how the Washington bill's cited "blocking technology" is supposed to work. If you load a pipe-shaped object into your CAM software, how the hell is it supposed to know if it's an illegal firearm part or just a manifold? Maybe before each time it generates some G-code, you need to submit a signed affidavit to the government, and they'll conduct an investigation. Three months later you can print your fidget spinner.
Didn't know this. It kind reminds me of MIME multipart messages (used in email attachments, MMS, etc.) where the header includes a "boundary" tag which the parser will look for to terminate the part. It feels strange, like it could be some injection risk where if the file knew what the boundary was going to be, it could desync the bounds and turn one malicious, inactive file into one or more bad files.
I've noticed diskprices.com getting increasingly bad with filters, probably because the source data is garbage with Amazon sellers trying to jam all the keywords into titles or descriptions/features..."M.2 USB-C 3.2 PCIE NVME"
This kinda reminds me of error correction, and where at some level you can have detectable but not correctable error conditions. Adding Bob is just like adding a parity bit: can give you a good indication someone lied, but won't fix anything. Adding Charlie gives you the crudest ECC form, a repetition code (though for storing one bit, I don't think you can do better?)
Going to leap hours I think is a sufficient kick of the can down the road, one is only needed every few centuries. Pretty sure something'll happen in the next 600 years that obviates the need for that though (nuclear war, asteroid, technological singularity, need for a unified solar system time...), so us hack programmers can assume all three of those things.
[1]: https://en.wikipedia.org/wiki/Synodic_day