How granular would the permission be? If web browsers start blocking all animation and post-load layout shifting by default, including CSS transitions and animations, this would encourage website operators to structure the page to coerce permission to animate in each document. For example, a website operator could make each page load blank other than a notice to the effect "Tap or click to view 'Title of Article' on Name of Site."

In my experience on laptops and tablets, I've found the exact opposite (eager loading) helpful in some situations with limited or no data. I would download an entire page on unmetered Wi-Fi, go offline, and read while riding as a passenger in a car or bus.

I sincerely doubt that 14,500 USD per year (full-time minimum wage) is near enough to pay for income tax, rent, food, health insurance, and a round-trip taxi ride every weekday in most of the United States. I'd be interested to read examples of budgets that you have in mind.

Recent graduates tend to be stuck with hourly food service and retail jobs. These tend to treat availability outside 9 to 5 as a condition for hiring, not to be doable from home, and not to pay enough for a taxi. Even a cyclist needs a backup during bad weather.

If you dig deeper, you'll find that AMD originally reverse engineered the *8080*, not the 8086. The two companies had entered into a cross-licensing agreement by 1976. Intel agreed to let AMD second-source the 8086 in order to secure the PC deal with IBM, who insisted on having a second source vendor.

There would have been no Intel success story without AMD to back them up.

(That actually would have been for the best. IBM would probably have selected an non-segmented CPU from somebody else instead of Intel's kludge.)

If someone happens not to have this privilege, then how would they go about traveling to or from work at night or on Sundays, when all the bus drivers are at home with their families? (Source: Citilink in Fort Wayne, Indiana, USA)

I imagine that most gamers are unwilling to pay for business-class service if business-class service is the only "real" service offered at their home address.

How are you going to host a game server on a home computer if you share your IPv4 address with other subscribers to the same ISP in the same neighborhood,[1] and the combined modem and router that your home ISP requires all subscribers to use lacks an option for port forwarding? Both of these are true, for example, of T-Mobile US Home Internet.

[1] Many home ISPs apply carrier-grade network address translation (CGNAT) to conserve IPv4 addresses since the worldwide exhaustion.

I once worked at a place that had a clean room process to create code compatible with a proprietary product. Anybody who had ever seen the original code or even loaded the original binary into a debugger was not allowed to write any code at all for the cloned product. The clone writers generally worked only off of the specifications and user documentation.

There were a handful of people who were allowed to debug the original to resolve a few questions about low-level compatibility. The only way they were allowed to communicate with the software writers was through written questions and answers that left a clear paper trail, and the answers had to be as terse as possible (usually just yes or no). Everyone knew that these memos were highly likely to be used as evidence in legal proceedings.

I highly doubt that any AI tech bros have ever been this rigorous, and I'd bet that most of these AIs have been trained on the exact same source code that they are cloning.

You're confusing the importance of avoiding Kessler syndrome in LEO with the difficulty of causing Kessler syndrome. GEO debris can potentially remain there for millions of years before interactions between the gravitational pull of the Sun, Earth, and Moon sufficiently perturb it. LEO debris remains for weeks to months. You have to have many orders of magnitude more debris in LEO to trigger Kessler Syndrome, where the rate of collisions exceeds the rate of debris loss.

The fact that a LEO Kessler Syndrome would also be short is something that exists on top of that.

It's also worth nothing that not only are modern satellites not only vastly better at properly disposing of themselves than they were in the 1970s when Kessler Syndrome was proposed, but they're also vastly better at avoiding debris strikes. All of these factors are multiplicative together.

Lol, I was thinking of this instead ;)

People forget that the primary concerns about Kessler Syndrome were about geosynchronous orbit, which used to be where all the most important satellites went (many of course still go there, but not the megaconstellations). It takes a long, long time for debris to leave GEO. But LEO is a very different beast.

They said it's internal rather than a collision, so probably a failed COPV would be my guess.

Yeah. In particular:

with fragments likely to fall to Earth over the next few weeks

LEO FTW. Kessler Syndrome is primarily a risk if you put too much stuff with too poor of an end-of-life disposal rate in GEO. End-of-life without proper disposal rates have declined exponentially since Kessler Syndrome was first proposed (manufacturers both understand the importance more, and do a better job, of decreasing the rate of failures before deorbit - in the past, sometimes there wasn't even attempts to dispose of a craft at end-of-life). And now we're increasingly putting stuff in LEO, where debris falls out of orbit relatively quickly. It's not impossible in LEO, esp. with higher LEO orbits - but it's much more difficult.

Or to put it another way: fragments can't build up to hit other things if they're gone after just a couple weeks.

And this trend is likely to continue - a lower percentage of premature failures, and decreasing altitudes / reentry times. Concerning ever-decreasing altitudes, we've already been doing this via use of ion engines to provide more reboost (with mission lifespans designed for only several years before running out of propellant, instead of decades like the giant GEO ones), but there's an increasing interest in "sky skimming" satellites that function in a way somewhat reminiscent of a ramjet - instead of krypton or xenon as the propellant for an ion engine, the sparse atmospheric air itself is the propellant, so the craft can in effect fly indefinitely until it fails, wherein it quite rapidly enters the denser atmosphere and burns up.

ED: "But it doesn't work for gravity with linear curvature"