6 Dec
2016
6 Dec
'16
2:17 a.m.
On Sun, Dec 4, 2016 at 7:25 PM, Gavin Lambert
Some use cases would naturally lend itself to one, while others would lend itself to the other. If all of the code is controlled by you then using Signals2 probably makes more sense, since it's trivial to include the signals in your own classes and it gives you better performance (in theory -- YMMV with mutexes).
This is exactly right, thanks. I'll just add that once you consider Synapse as part of your arsenal, you'll probably see use cases you're not thinking about right now. I even ended up rewriting several systems in my own code base to use Synapse, which made them much simpler and more elegant. Emil