I think Salesforce is downplaying that After-Save Flow Triggers are bad. Am I wrong?

Salesforce’s Architecture Decision Guide on Triggers argues that

• we should move all our automation to “no-code” Flows or “pro-code” Apex
• because Workflow and Process Builder are being retired.

But but but. In the weeds of the article, there’s a comparison of different automations:

I read that comparison like this:

. . . and that imo puts After-Save Flow Triggers in the Process Builder camp of slow, bad automation.

Diving a little deeper, there’s a second experiment and graph:

Edward Tufte would deride this for looking like the previous chart, but measuring something very different: multiples instead of milliseconds.

In any case, the upshot is similar: After-Save Flow Triggers again fall into the “bad” side:

Thanks to Melissa Shepard for bringing my attention to it!