I am a big fan of messenger library. While there is a learn curve it is open enough to let users use the library with the own style. Every part feels well thought-out, it doesn't have the short comings of DQMH's poorly implemented cloneable for example.
With my own framework, which is inspired in ways by MF, one thing I have done to help new users is to separate out the logical of modular code and dynamic (start async) launching. This helps traditional producer consumer type people get on board where they can still 'see' the async module on their main block diagram but the same module could be launched as with MF actors.
One pain point I have with the dev template: As it inherits from the JKI SM the passing around case specific data (transient data) as a string rather frustrates me. I like the classic message string and variant data.
I would also like some larger examples maybe show how best to implement OOP and interfaces in a type safe but extensible manner
