Exactly! That's a point I didn't want to raise too much because in my case Yarn will support third-party plugins (because of the second reason mentioned), but in the case of the first this is spot on.
Whether to build a modular architecture and whether to allow third-party authors to use it are two different decisions. Even a private plugin architecture may yield benefits just by enforcing some structure during the development.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The monolith should seek a similar architecture as the plugins system. As you say the plugins system forces you to define the api of a core.
The difference I would say is that a monolith knows all of its extensions, this means the api can change wholistically without a depreciation cycle.
Plugin architecture without the Plugin system.
Exactly! That's a point I didn't want to raise too much because in my case Yarn will support third-party plugins (because of the second reason mentioned), but in the case of the first this is spot on.
Whether to build a modular architecture and whether to allow third-party authors to use it are two different decisions. Even a private plugin architecture may yield benefits just by enforcing some structure during the development.