> If you find a bug with the adhoc framework you need to convince a busy person in another team to spend time to unblock you.
Which is not so difficult, because that busy person is in the same organisation as you, and therefor working towards the same goal.
Fixing that bug is much more difficult if that person is in an outside organisation, serving many other customers on the same code base (with possible conflicting needs), and/or is not actually in any way accountable for it (open source).
> Which is not so difficult, because that busy person is in the same organisation as you
Hopefully. But not necessarily. This argument is spinning in circles. In house projects can be abandoned just as oppen-source ones can. For me that was Powermock for example.
People knowing a framework will often use it for everything. Instead looking at the problem and find the easiest solution to it offers great time to marked.
I've proudly deleted more code than I've written at work.
The easiest solution you can imagine. These are 90% of the time cute tricks that narrow down the scope of the solution so far it makes the surrounding code unmaintainable after a year.
I learned to call those people "Ricks" they are best used in walled of projects that are not expected to change. Not useable in cooperation.