3 ms·
What is the incentive for the main project to build their software this way? It would likely be a lot of work to split up the software in modules like that. The
by Thiez 4y ago
What is the incentive for the main project to build their software this way? It would likely be a lot of work to split up the software in modules like that. They would either regularly break backwards compatibility, negating the advantages of these modules, or they would have to bind their hands forever, unable to evolve the design and module boundaries. All to support forks that probably never get merged back into the main project, so from the main project perspectives the dev time is no less wasted than before. Except that they now wasted a lot of dev time to do this thing that doesn't bring them much, if anything.
This RPC stuff would likely also be slightly slower, so people would just say Firefox is slow and use Chrome.
- layer8 4y agoSeparation of concerns and improved testability could be an incentive for such modularization.
- funcDropShadow 4y agoBeing able to join forces with more co-developers can be an incentive ... and a burden, to be honest. But for some it situations it could be an incentive.
- omniglottal 4y agoThe comment to which you are replying points out the obvious value of such a proposal. Your not seeing immediate value, else suggesting it is not valuable, seems to be your error. All projects benefit more from those who see value in an effort, who are willing to put in that effort, than those discouraging or subverting such effort, given their ignorance of such value.