They're addressing the same need and yield the same behavior patterns and thus will have the same organizational outcomes

I talked about it in a currently unfinished blog post, here's the section

"In the 2000s and 2010s, this was the core conflict of frameworks. Does the framework have enough alignment with the task that it would cumulatively simplify things.

However, this is not how we behave. Instead habituation promotes einstellung where we end up relying on the tool of the AI to do the trivial. This is closely related to Automation bias and OOTL."

It's not complete but here it is anyways

https://blog.day50.dev/intro/vibedrift/

Things like the einstellung effect are important in vibe coding, software design and framework use. It's a truism about meta tool use and the relationships and behavior systems that accompany them along with the epistemological edifices they prop up. Quoting Wikipedia:

"After solving many problems which had the same solution, subjects applied the same solution to later problems even though a simpler solution existed"

I should get back and finish it probably by this week.