It looks like container2wasm uses a forked version of Bochs to get the x86-64 kernel emulation to work. If one pulled that out separately and patched it a bit more to have the remaining feature support it'd probably be the closest overall. Of course one could say the same about patching anything with enough enthusiasm :).
Leap seconds have so many problems beyond the time adjustment. It's a small/odd enough adjustment interval that there are wildly different approaches like leap smears. On top of being so small, it's rare enough (~every 2 years), depending on how a system is used, lack of proper handling might not be obviously apparent or lack of obvious problem in one implementation ignoring it may lead to lack of care in another implementation which would have a problem ignoring it.
Leap hour replaces all of that with what is more or less equivalent to a change in DST rules (except for more time zones at once). DST changes don't go perfect either by any means... but we do them regularly enough without the world crashing down that doing an additional shift change of an extra hour every 5000 years is almost certainly less hassle and breakage than the leap second approach breaking things every ~2 years.
It is way more easy to let UTC (without leap seconds) just drift away from the zero meridian and move countries to different time zones when convenient. We mess around with daylight savings time often enough that nobody will notice if we have change local time every couple of thousand years.
DST changes are pre-scheduled. Throwing a random hour in/out at (say) June 30, 2029 may be something else. Unless the jump is treated as a TZ change in tzdata?
Yeah you treat it as a time zone change where every zone moves over (or every country moves to the adjacent zone maybe). You can schedule it N years in advance. It's definitely not 0 disruption, but it's very manageable. Regions change TZs or toggle DST frequently enough that we can handle it.
The bomb was built with decision to delay shipment until the 13th to see if Japan surrendered. On the 13th no word had come, but the shipment was further delayed to wait for word anyways. On the 14th word of Japan's decision to surrender was announced. https://www.marshallfoundation.org/articles-and-features/gen...
Had the bomb already been shipped, nothing about these delays suggests it would have instead been dropped before surrender instead of just delayed there. In reality, the pause sources from when Truman intervened immediately after Nagasaki (which was bombed on the 9th, Hiroshima previously on the 6th) by the 10th in hopes of unconditional surrender instead.
Had Japan not surrendered for some reason (they had more going south at the time than just the nukes) the US may well have dropped a 3rd bomb over another approach. That said, I'll give due credit to Truman that the activity was paused on hopes of surrender first rather than waiting for the next one to arrive.
> Zero interest-rate policy (ZIRP) is a macroeconomic concept describing conditions with a very low nominal interest rate, such as those in contemporary Japan and in the United States from December 2008 through December 2015 and again from March 2020 until March 2022 amid the COVID-19 pandemic.
Not quite everything. Some of the page doesn't load and not all of the functionality works but it is nice enough to let you try to view the parts you can rather than either force it to not load or act like the entire page loaded fine.
You can get Strix Halo in mini desktop form factor but they won't be AM5 socketed because roughly 1/2 to 3/4 of the memory bandwidth would need to be missing, starving the massive iGPU you just paid for.
Following this process summarizes the blogpost for me. Perhaps the difference is I'm signed into my account so it can access external URLs or something of that nature?
Most will at least want something like https://brew.sh/ to get you current versions of standard Linux utilities rather than the bundled ones and then maybe even set up a separate profile in your terminal of choice (iTerm2 is a great option as well) which defaults to using them so you don't break normal system usage which assumes the built in utilities.
Even then, if your use case requires using standard Docker images, assumes certain features of the kernel, or assumes common distro environments rather than just you wanting a posixy feeling terminal you'll still need to run a Linux VM in the background.
reply