Lots of people asking here for this clear definition.

If you understand this well, please lay it out here in a straightforward manner.

To me, Alexithymia alone proves this.

Hand-waving assumptions drawn from narrow subjective experience without awareness of the profound and contradictory results that have come from scientific study of consciousness and causality.

Increasing latency can also reduce TCP throughput ceiling, increase in-flight concurrency, and increase server memory consumption.

Wire protocol applies to external interaction with the db.

Internal ABI/API is used by extensions to directly interact with core subsystems and depends on internal models for things like storage.

It might be analogous to HTTP versus an nginx plugin.

curious how hard it is to implement wire protocol compatibility vs the internal api surface. Are we talking like, an order of magnitude more work here? I wonder if, for example, Aurora team are literally maintaining forks of extensions for their implementation and that's why only a subset of all possible extensions are supported?

Of course market participants agree?

Exchanges have calculation rules for every type of mark and payment and will always specify rounding.

Paris would need significant infrastructure work across the distribution system to handle AC at NYC’s rate of 90% on summer heat wave days.

Sure he does.

It's not handwaving to complain that shipped features are never completed and a functional CLI for fundamental and critical tasks is never delivered.

The same way you get value out of a dev container.

Regulators don’t want to provide arbitrarily detail into their interpretation or likely judgements on issues that may come up for many reasons, good and bad.

One good one is that providing concrete razors for compliant and non-compliant behavior accelerates the gaming of the rules.