No doubt manufacturers will us this as an excuse to force users into buying a new model, blaming Microsoft in the process.
3,183 karma · joined September 13, 2015
A small nitpick. FOR UPDATE SKIP LOCKED was mainstream (in a sense) way before it was copied from Oracle to Postgres. It's used under the hood in most non-trivial Oracle deployments. Like for replication or refreshing materialized views in parallel.
Do we really need to remember them, instead of just writing them down?
For me two main drawbacks are no traffic and slow route [re]calculation, because it happens on device.
Can you share some examples of such images/fragments?
That's actually a reasonable security requirement, greatly narrowing attack surface. Note that ETW API was designed before CPU timing side channels like Spectre were a thing.