And my 4x point understates things, because I counted "human nuclear power" from 1942 when it should really be counted from, to be generous, 1951.

And of course that was over half a century ago. There have in fact been considerable advancements in many areas of science and engineering in the meantime.

The first (human initiated) self sustaining fission reaction was in 1942. The McMurdo plant went into operation in 1962. There has been over 4x more time between the start of that plant's operation and today than there was between the beginning of human nuclear power and the inauguration of that plant.

And, yes, any "shipping container" style reactor is necessarily going require a bunch of shielding relative to the size of the reactor itself. That's one of the inefficiencies of small scale reactors.

Fundamentally you have this backwards. This process is a compliance tool, not a recruiting tool.

If you want to sponsor someone for permanent residency, you need to do this PERM process. If you're in the PERM process, you already have an employee you are happy with, who was already allowed to enter the country on some sort of visa that allows them to work, but you're essentially required to post a job opening for them to notionally demonstrate they aren't taking a job from an American -- which is broken because, to the extent they did, they already did that probably years ago. Today they have an employee that's most likely been working for them for years that they're happy with enough to be willing to sponsor them for permanent residency.

The upshot is that this job posting part of the PERM process is fundamentally adversarial. You're fundamentally competing with some employee the company is happy with -- enough to sponsor them for permanent residency. That person is already ramped up on their projects and already performing well. Practically speaking the company has every incentive to say that you don't meet some fine print ultra specific requirement that they wouldn't care about if they were truly looking to hire. (and then maybe maybe they have other positions with different requirements for which you might be a fit.)

And, if you succeed in all this? Congratulations, you've fucked over someone trying to get permanent residency, and the employer in question isn't even obligated to hire you.

Pragmatically speaking, as a job seeker, PERM is fundamentally broken. (and it is broken, again, because it is controlling the wrong end of the process. The time for this sort of test is when granting work visas, not when granting permanent residency.) The only thing these job posts are potentially useful for is giving a snapshot into parts of a company that don't necessarily have active job posts, noting that there is a bureaucratic incentive to be as specific as legally permissible regarding skillset. At that point you should engage with the company using other non adversarial avenues such as networking or just going through the "front door" normal recruiting process.

What "felonies" are involved in "hitting the high seas for their streaming content" (in the United States)?

Note that criminal copyright infringement in the US requires that it be "for purposes of commercial advantage or private financial gain" which almost certainly wouldn't be met by even something like running a bittorrent client where you're distributing copies to other people.

You joke, but 4 to 5 would be the right number if they could magically work out all the engineering problems.

The biggest problem for 2-fold is that if you start with a a standard widescreen 9:16, unfolding gets you 18:16 -- a glorified square. It's nice for content that doesn't care, and is awesome for tankobon comics which are 7:5 and painful to read on a normal phone. On the other hand, the unfolded version doesn't get you much extra space when viewing standard widescreen video -- it's a small improvement but the vast majority of the extra inner screen area gets letterboxed. A third fold would do a lot to fix that.

Except that phones are typically taller than 9:16. For example, the Pixel 9 and 10 folds are 9:20. (and then the inner screen is 1.04:1). That means you need a 4x fold to get to 16:9 when unfolded, and then a fifth fold would get you approximately the original phone aspect ratio.

If it doesn't "reprocess anything but a tiny amount" it doesn't "solve for a highly radioactive and dangerous problem".

Note that bill C-3 in Canada back in December 2025 changed how birthright citizenship works, and quite a few people who were pretending might not need to pretend anymore.

Except of course if you're sophisticated enough about this to complain about it, you're sophisticated enough to know the specs of your laptop ports, which addresses 90% of what you're complaining about, and much of what is left is actual manufacturer defects, bugs, or flagrant misimplementations.

Like, set aside "physical connection" and "protocol" -- to a 99% approximation, connection of a laptop with DisplayPort alternate mode to a USB C monitor should work on any laptop/device that supports DisplayPort alternate mode or USB4/Thunderbolt which mandate DP altmode support.

The same docking station having issues with identical laptops may very well have been a hardware/firmware bug of some sort. Note that there was a widespread firmware bug in Lenovo Thinkpad hardware in the 2017-2019 timeframe that would cause it to constantly write to SPI-ROM on the Thunderbolt controller and eventually wear it out and cause it to fail in weird ways.

I am all for making DST permanent, but can we not make it take effect in a matter of a few days? Times falling out of sync can cause any number of random issues, and there are plenty of systems out there for which the "speed of light" time for a software update is weeks or months. (This is particularly a problem for Windows systems that to this day by default persist in the mistake of having the hardware clock be in local time.)

I think you have some fundamental misunderstandings here. First off, there absolutely is an amount of "hot spares and RAID" that would save you from "failure rates that high", and ultimately hot spares aren't going to help anyway -- either you're actively running things in which case you need enough hot spares to handle disk replacements until the next time someone opens up the computer in question to add more disks, or at the opposite extreme you need enough active redundancy to survive a random 1/3 of disks failing. With that said, it sounds a lot like you think the model here is "a bunch of drives sitting on a shelf", which isn't how anyone sane would run this type of service. The Backblaze model (at least as of 2016 when they last published POD designs) has all disks actively connected to computers. Those 2016 designs heavily use expanders which means that you're not going to get full bandwidth to all disks at once, but it's not like the disks are powered down and inaccessible. It almost certainly makes sense to use spare disk I/O bandwidth to run some frequency of scrubbing of existing data -- if only else to figure out quickly when disks fail so you don't need to keep so much redundancy around. Like, think of this as weeks to months between scrubs that verify that all backed up data is healthy, not accessing cold data after disks sat on a shelf for years.

A fundamental problem with "remote controlled by the cheapest of workers somewhere on earth" is latency. Just considering network latency, you're looking at hundreds of milliseconds of round trip time if you try to have (for example) people in India remote controlling a vehicle in America.

That might be fine for high level executive directions for an AI system, but it isn't going to work if you want them to actually take over and drive the vehicle. The latter really needs someone probably within a few hundred miles.

The main point of a support structure like the one apparently negotiated here is exactly to provide enough time for a migration to happen, should VMWare or its successor company/companies decide to dramatically change the terms/prices of the products in question.

Like, if VMWare suddenly got 100x more expensive, that's fine -- they'll just move away to something else, but such a migration takes time so they want locked in non-price-gouge rates for enough time to actually do that migration. Additionally, having such a support guarantee would make it more possible to take advantage of VMWare specific features that would make it more difficult to migrate to something else.

The problem is that Broadcom and/or the supplier appear to have reneged on at least the spirit of that deal.

I assume the "just switch" will very likely happen. The point is to give Tesco enough time to actually do that switch.

I am just slightly confused here. You're talking about "defending violent criminals" while the Trump administration itself appears to be mysteriously reneging on their own promises to release details about a notorious child sex trafficker with close historical ties to Trump, even while that same administration mysteriously moves his closest accomplice to a minimum security prison.

No amount of deployment of national guard to DC is going to solve the criminal gang problem if the people issuing their orders aren't even pretending to not be regulars at that Pizzagate place.

Castle Bravo is a somewhat odd example to bring up in the context of Lithium 6 versus 7: Lithium 7 fissioning from high energy neutrons and producing tritium was the reason that Castle Bravo was 2.5x larger than expected.

I'm not sure what fantasyland Japan you're living in, but 10 gigabit fiber service is nowhere near as ubiquitous as you're saying. It certainly exists, but it isn't "the basic fibre service" -- it is a still somewhat limited area availability product, and unless something has changed in the past year or so it is a premium product that isn't the lowest tier of any provider.