Dynamics 365 Processes vs Power Automate (Flow) features missing (limitations)

Many Dynamics Developer or Citizen developers still get perplexed regarding what will be the best way to execute extended logic for Dynamics Platform. On top of that Microsoft keeps on promoting to use of Power Automate (flow) to execute the extended logic. Still, I see Power Automate is lagging to give more options to execute logic as Dynamics Process does. So thought of to highlight the main limitations of Power Automate flows for the Dynamic platform.

1) Dynamics 365 Process (Workflow) can be real-time however same we can not expect this with Power Automate. 

2) Can't run custom workflow activities, to execute the logic from class library .dll.

3) Can't access pre-image event data from pipeline execution before hitting the database transaction.

4) Wait conditions don't work the same way as they work in Workflow.

5) Another thing this might be for developers :-) I don't like the Power Automate when the logic expands which grows the tree like anything. Not easy to read the logic like we read the code in Dynamics workflows. 

However, we cannot deny Power Automate gives other in-built powerful features like  Parallel branches, Out-of-the-box connectors to external systems, Approval workflows, Run on Schedule, Analytics, and AI-assisted authoring.

From a developer and maintenance perspective, I love to keep the logic in one place. For example, for the client side form, I don't love to write half logic in javascript and half logic in Business Rules.

So keep the above points in mind while deciding what to choose to extend the logic for Dynamics platform.