3 ms·
Another alternative is to build a stable plug-in API rather than handling such requests in the core product. That way users with particular needs can code their
by nradov 5y ago
Another alternative is to build a stable plug-in API rather than handling such requests in the core product. That way users with particular needs can code their own plug-ins rather than forking the entire code base. Now obviously open source maintainers have no obligation to do that, but purely from an engineering perspective it's an approach worth considering.
- pjc50 5y agoYou then hit the two problems that everyone with a plugin API hits: - you can't rearchitecture your software beyond a certain amount without breaking the plugin API - if a plugin crashes, people will blame the host, no matter how you attempt to deflect this
- GoblinSlayer 5y agoThat's what log4net does, and presumably log4j has a plugin api too.