This idea is super cool. I am not sure it necessarily has to be just one single dependency, but keeping the number of dependencies as low as possible makes a l

This idea is super cool. I am not sure it necessarily has to be just one single dependency, but keeping the number of dependencies as low as possible makes a lot of sense to me. At least the overhead of introducing any given new dependency should be taken into serious consideration and held against the concrete benefits that will be gained from it. I wrote a blog post on a very similar subject, essentially all of the same arguments, but targeted more towards the dependencies and abstractions found within a given systems code structure and application architecture. If you are interested, you can read it here: https://betterprogramming.pub/avoiding-premature-software-abstractions-8ba2e990930a https://betterprogramming.pub/avoiding-premature-software-ab...