he/him 
For the last few years I’ve been strongly swaying from “monolith tools” to “plugin everything”. I don’t think either approach is actually sustainable. Likely need something that’s a mix. Not sure what it would look like though.
-
What if the monolith has a plug-in system with caveats made obvious to the end user, and plugins that work especially well are from time to time brought in as first-party?
Yeah that's a model I think could work. Another problem comes with exposing plugins in a monolith. The API surface can be massive and prevents being able to make large changes, which is one of the compelling reason for a monolith to begin with.
-
-
Webpack does this and folks fault it for the massive API surface.
-
Tapable just makes it too easy to add hooks
By far my favorite way of making a package pluggablehttps://github.com/webpack/tapable - 3 more replies
New conversation -
-
-
That’s almost literally RoR. I’d love to see similar in Node land.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We’ve been making these decisions in
@SwaggerApi UI over the last couple of years - we expose almost all of the project’s internals through a plug-in interface. The interface itself is contract, but the underlying implementations that users can touch are subject to change.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.