samus

I'm not aware of any way to find that out as an application. Even if it exists it will probably be a full system call and therefore prohibitively expensive to defensively do it everywhere.

Databases can do this via the page cache since that's basically an implementation of swapping where the DBMS has full control.

Edit: anyway, the problem in TA was that GC metadata had to be accessed. The GC cannot delay this. It might decide to abort the stop-the-world phase so the application can continue while GC metadata is swapped in, but then one runs into liveness issues since next time the GC runs it might already be swapped out again.

You keep the old repo for archival purposes and work with the new one.

The switchover date is usually announced well in advance and any interested parties can easily verify that the conversion was authentic.

Every file (indirectly) referred to by a SHA256 commit using a SHA1 hash in some tree object can still be spoofed. Fixing that requires rehashing all objects and recreating all tree objects so the tree objects referred to by SHA256 commits are purely made up of object references computed by SHA256.

It seems Fossil can use multiple hash algorithm within the same repository. Yes, that decreases overall security since the hashes pointing to older objects can still be spoofed.

At least these installations don't need to deal with radioactive material directly, so they will have the same financial infact as similar improvements to, say, coal-fired power plants.

A more natural way to see it is that Chinese does not really have tenses in the first place.

You don't understand. They will make you pay for it by charging a handling fee. How about $10 flat per transaction?

Many banks nowadays charge higher fees for teller service.

At the end of the day the developers have to work with logging and error messages and exception stacktraces that the production system spits out. Also, operations personell needs to be able to diagnose issues and handle them or give good bug reports to develops. The above concerns should dictate how to best handle errors, and developers should figure out how to best accomplish this within the constraints of their tech stack.

There are several valid ways to do this, but it's important that one strategy is agreed upon and abided to, at least in new code. It's important that one srrategy becomes the orthodox one, else there will never be a reckoning about its effectiveness, but instead only people clinging to their own standards on their own turf. Legacy code complicates the picture of course.

The impact is rather that is explains the failure of attempts to cultivate cell cultures of brainstem cells.

I heard adipose tissue also retains hormones and fat-soluble pollutants, and losing weight releases them and they have to be dealt with by the body in other ways. Specifically, the hormones can cause mood swings, which some individuals have learned to react to with binge eating.

Fill your freezer with frozen food other than ice cream.

The digestive tract could also be seen as a single organ since they are connected. I think the deciding criteria should be the one applied in this study, i.e., how an organ develops.

> It should probably be noted that this specific case led to a conviction of an actual crime (Bank fraud and money laundering).

That's pretty much irrelevant to the discussion. Of course a lot more crimes would get prosecuted if we lived in a total police state.

The problem is the 100 mile rule, which effectively puts most of the population under the purview of border control measures.

Apart from that, an airport is a comparatively small area of land that is magnitudes easier to monitor than a border that only exists as a thousands of miles long line on the map, therefore the 100 miles rule should not be applied. And everyone getting off an international flight in the USA has already been searched multiple times.

How is the law subverted if one doesn't make all data immediately available?

> It’s hard to say what happened but these collapses sometimes have paradoxical outcomes e.g. we have evidence that the quality of life and health improved for Western Europeans at least in some places after the Roman Empire collapsed (less population pressure, no crippling taxes etc.)

The collapse of the Western Roman Empire was not an instantaneous collapse of civilization altogether, just of Rome's control over the empire being snuffed out for good. Already long before the final collapse the people in charge (which were not necessarily the Emperor) had only very tenuous control over large parts of the empire.

Full civilizational breakdown happened in a few places only, like Britain or southern Germany. Italy was widely depopulated because of the various wars between the Goths and the Eastern Roman Empire trying to recover the western half.

One still has to do field work to gather all the linguistic data. It's rather easy with settled societies only. Researchers studying indigenous languages had to travel to hard to reach places and often live with the tribes for a quite long time.

It's a lot easier nowadays, but ease of transportation also correlates quite well with a levelling of linguistic distinctions. That's a problem because the comparative method of reconstructing older stages of a language relies on the assumption that different dialects maintain aspects of the older language.

"die See" refers to the sea in general, not to a specific body of water, unless it is part of a name, like "Nordsee".

The English word "sea" is also sometimes used in this sense, but it's less apparent since "the" carries no gender: "He liked living close to the sea." - doesn't really refer to a specific sea or ocean even though the definite article has been used. (I'm happy to be corrected if this is an ungrammatical sentence since I'm not a native English speaker)

Stealing in this case is not about physically removing something from one's possessions, but more about disguising attribution and in many cases also reducing a future income stream.

You can go with a lot less code if you don't care about proper cleanup of resources.

The argument was not about stopping Chrome from becoming integrated into Android.

> It's easier maintaining a fork of Blink than an entirely different engine. Google being the primary maintainer doesn't mean that browsers can't make large forks.

Maintaining a fork is not fun as taking patches from the origin repo becomes more complicated the longer the fork exists and the bigger the divergence becomes.

> How is having N engine developers implement some new addition to the EMCAScript or CSS standard for each of their engines not duplicated work?

It would be duplicated only if they all maintained, say, a Blink fork.

Except one does since Google is the primary maintainer. Anyway, work on other browser engines is not duplicated or wasted.

And that market share is maintained by integration with Android and low-key sabotage of others browsers, especially Firefox. Similar to how Microsoft maintained its monopoly decades ago.

Sanctions

Nah, withers are generally useful.

I mean, it's a smaller issue in a K8s environment as it will just spin up a fresh pod.

Yes, that's what they do. The brine is stored in huge pools next to the extraction site.