samus

I just don't get why you treat this as something super complicated. There is street and nature level dirt which contains an unknowable degree of contamination that can be unambiguously bad for you if you ingest it, no matter what that BBC article says, and the inside areas where people eat and sleep. The vast majority of cultures prefer to maintain that separation and to maintain a considerably higher level of cleanliness in the living areas, no matter if it's not at semiconductor fab level.

Specific to Japanese culture is just that they prefer to sit at low tables and to sleep on the ground on duvets; it should be easy to see why they want less dirt on the ground than other cultures.

The toothbrush is a moot point if you have a separate be bathroom and toilet. If they are combined the spread of fecal particles is curbed by flushing the toilet with closed lid. And in the end the toothbrush is flushed before using and then coated with toothpaste, which often contains detergents and microbial agenda, and which is finally flushed out.

I don't think you can conclude from that incident that all soap is always contaminated. And even if it's not perfectly clean, in the end ist's all flushed away.

I don't really get what your point is. Are you regularly eating from the pedestrian way?

The living area is usually elevated and so you can simply sit down, take off your shoes, and easily change into slippers that are ready at the edge of the living area. Or, one simply steps out your shoes (easy enough at least with sneakers) and to the living area. Easy to do unless one is infirm.

That poster wrote about speculative vulnerabilities. But buffer overflows have nothing to do with those.

Indeed, but that's orthogonal to soldiers bringing their phones on deployments. They can also be recruited and handled when there's no way to separate them from their phones, i.e., off duty.

> The reason why the Tokugawas shut the country's borders for hundreds of years was because they understood that Christian missionaries were a front for a larger invasion force that would pillage the country's resources and abduct people to become slaves in other countries.

They simply didn't want another religion. Buddhism was already troublesome enough with a long history of popular uprisings and many monasteries having become as powerful as daimyos. Oda Nobunaga had been mostly tolerant of religions and also of Christians, but he is infamous for bloody curbing their power. The Tokugawa didn't want any of that from happening again, regardless which religion.

There was also a strong motivation to deflate the power of the port cities. They were often in the hands of untrusted daimyos because the Tokugawa prioritized controlling inland regions with farmland and important road connections to keep the economy running and to ensure that troops could be deployed everywhere and kept supplied in case of rebellions.

Sure, but there are a lot of non-western cultures out there. What's surprising is the prevalence of posts regarding Japanese culture.

Our feet were not evolved to walk over stone and concrete all day.

Of course one should not put the feet down where the shoes are stored.

There are currently no large-scale deployments against them though. Of course the US is going to learn the lesson painfully if they don't take care of these information leaks.

Large-scale troop mobilization are not subtle and can be sussed out by satellite observations. You can bet that all US forces are already closely tracked that way.

Invasions are usually spearheaded by elite forces that I presume are competent enough to understand that actively broadcasting what you're about to do is a bad idea.

The US is currently not deploying troops against an adversary that can make use of that information.

The US military hasn't yet been in a military altercation with a peer adversary that can actually exploit that information. The war in Ukraine shows that these information leaks can have severe tactical consequences.

Every time someone has that idea they discover that text editing is hard! Kudos to the author that they considered accessibility as well.

I guess it's for people who only have a smartphone. Or a potato that is ok for browsing, but not for FPGA synthesis.

The GDPR doesn't directly mandate cookie banners though. It wants consent from users prior to processing their data.

Also, the browser flag that indicates no consent already exists: https://globalprivacycontrol.org/faq

Why would they do that? That would make their shareholders angry and give their competitors an edge. (No /s)

Wal-Mart has a direct, strong financial motivation to maintain that public bathroom: Customers that have to leave because they have to go to the toilet will buy less things.

> Any person without serious mental and/or substance problems can handle losing their job without sleeping in the streets.

This statement is very load-bearing in your whole argument though. Losing a job can completely derail a person's daily habits and cause their issues to worsen, either by the additional stress or by forgetting to keep their meds. It's downhill from there.

> I think you'd find less graffiti in a rural bathroom than a large city bathroom.

IMHO that's purely due to differences in population density.

My second condition would reject the additional element, as it would not be found in the input. have to be duplicated to However, I was lazy about the `|input| = |output|` constraints. With those constraints it would not be possible to omit elements from the input in the output.

Trivial one: `forall i, j. 0 <= i < j < |sorted| -> sorted[i] <= sorted[j]`, which can be satisfied by copying a single element from `input` or by `sorted` being empty.

It can be fixed (feedback welcome) by adding: `forall i, j. 0 <= i < |sorted| -> |indexof_id(sorted, input[i])| = 1`, with `indexof_id` using equality by identity, which is crucial in practice.

Note that the amended definition implies quadratic runtime, which is the crucial difference between a specification and an efficient implementation.

To some degree these are the same things, depending on the type system. But it might be easier to write a function accepting a list of size 3 than matching on a constraint, which might get separated from the variable it annotates.

> The question I always have is "why would the formal verification be any more correct than the program it is verifying?", Note: not bugs in the verification engine, but the spec made for the program.

It is a nothingburger problem because one is going to have that problem as well even when not employing formal methods. Except without FM the spec will be in natural language and therefore it will be impossible to mechanically verify the end product with it. And since natural language specs are highly liable to be ambiguous or contain unintended holes, LLMs won't save us either.

Yes, human direction will still be required for the foreseeable future (whatever that means in this fast-paced field) to recognize where introducing a DSL or a macro makes sense.

Common Lisp is unfortunately a merge of multiple competing Lisps from the time period, much like Unix (SysV and BSD stuff). It was probably reasoned that a messy, imperfect standard is better than no standard or a restricted standard that is useless without proprietary extensions and requires constant revisions by a standing committee. There are good reasons to deviate from it and come up with a cleaner Lisp, but people better learn all the lessons Common Lisp has to offer before they do so.

It's inefficient, but still better than completely losing out on it. Better yet would be direct reuse or remote heating.

It might actually be safe to use as a condiment, as originally intended.

This is not rot, but digestion. The digestive enzymes of the fish keep breaking down amino acids, producing the characteristic smell. The salt prevents most microorganisms from growing.

Killed from what? It's essentially sterile from all the salt.