I don't quite understand it, so just to be sure: Instead of fixed calls to other modules all modules use this library to call other modules' functions? I thin

I don't quite understand it, so just to be sure: Instead of fixed calls to other modules all modules use this library to call other modules' functions? I think everyone has that idea at some point. I started writing my own but ended up going back to rigid coupling because unless I really decouple the system, for example to place modules in different processes or even machines, or letting different versions of certain modules "plug in" simply by loading them (run-time configurable) instead of having to change module names all over the code (needs to be done before deployment), it didn't really give me any benefit (at that early stage). I still use it for logging: I don't have to call a specific method, instead it's all just "messages", and when I have a "logger" listening for certain messages it logs them on the console, in production I'd leave the calls in but send them to a server, simply by loading another logger module, without code changes. My statement is only for my own specific project, I found that whether to use such a method or not is highly specific. So my only point is that trying to use such an approach "because it sounds cool" turned out not to be sufficient reason. IMHO the provided "Motivation" document is not sufficient (https://mbasso.github.io/refraction/docs/introduction/Motivation.html https://mbasso.github.io/refraction/docs/introduction/Motiva...). I think more could (should?) be said and explained.