Iem3ohvi

The fluids also contain various electrolytes, i.e. metal cations. But still nowhere close to those trees.

> Dr Antony van der Ent

Nominative determinism strikes again

Well, that just isn't happening and hasn't happened for years. So someone stepping up to define a standard focused on performance is a good thing in principle. You also need incentives for that standard to get adopted. Of course google shouldn't be the only player here, others should participate in this too.

Dynamically generated code, e.g. proxy classes and aspect pointcuts being inserted into code and then recompiled by the JIT.

And even "just" dynamically loading a library requires recompilation because it will invalidate optimizer assumptions such as devirtualization (part of class hierarchy analysis in hotspot).

It has been listed on the arch wiki under their list of available terminal emulators for a long time and I often use the wiki to look up things even when having to configure things on non-arch systems.

amp.js? No thanks. A blessed subset of the HTML, CSS and media that is optimized for load times and memory footprint? Ok.

All the heavy lifting for containers is built-in. It's just the mapping of tabs to containers, the creation/disposal of containers and UI parts that's managed through the extensions because users do have different preferences and use-cases in that area. E.g. they may want automatic rule-driven assignment of domains to containers except when either blah blah holds or when manually overridden.

The built-in minimal and completely manual UI can be enabled with privacy.userContext.enabled = true

> Unless the programmer is programming at a very low level

If you write unixy tools that do just one job then you often have to deal with this. For example rsync and tar put files into sequential mode and perform readaheads or writebehind-drop the page cache.

And it's not just that kind of tool. At $JOB I did a fairly simple optimization to significantly reduce loadtimes (from NFS) in a render farm by importing a 3rd-party library which provided the necessary libc bindings for readaheads. It's only a dozen lines of code but reduces user-perceived latency from minutes to seconds. The PO was quite happy about not having to pay for hundreds of NVMe SSDs.

I recall a new transatlantic cable constructed a few years ago being advertised as shaving off a few milliseconds. Trading and cloud providers were mentioned as target customers. I don't know whether they also route public internet traffic.

Technically neutrino signalling could make it faster, but those extra milliseconds are not worth it, even for the HFT folks... but thanks to them we have shorter fiber routes across the atlantic at least.

Averages are not particularly interesting. CDFs or violin graphs are since hundreds of requests to load a site can turn your 99th percentile into what the user actually experiences.

Edit: I just noticed that clicking on it shows box plots. Good enough!