4 ms·
I generally agree, but publish/subscribe can also lead to a spaghetti of messages. In big apps you can get so many messages you start to lose the big picture an
by BonoboBoner 16y ago
I generally agree, but publish/subscribe can also lead to a spaghetti of messages. In big apps you can get so many messages you start to lose the big picture and can no longer tell "who calls what? what is the sequence of control flow? etc" It is a great model, but as anything is, it is not a silverbullet.
- kls 16y agoRight, which is why I framed it in the context of UI development. A good deal of UI apps are not a deep but broad problem set. Generally there is not great depth of chaining to the point that you need deep stack logic or techniques. For many web apps it is simple format/display and update data. Even deep apps (for web apps) like mapping or trader applications are simply variations on this theme. In that context it is the closest thing to a silver bullet we have to building rapid and extensible UI's while maintaining quality controls.
- naelshawwa 16y agoExactly. This style suits the UI very well because of te nature of it. At the end, the UI responds to events whether they are user driven or system driven ex. Notifications. One of my favorites is the ability for the UI to degrade gracefully even if a component has been removed because nothing calls it directly, just publishes to it.