4 ms·
I know it's naturally happening in a large codebase, I'm asking why they specifically maintain a fork just for that instead of trying to push what are probably
by KolmogorovComp 2y ago
I know it's naturally happening in a large codebase, I'm asking why they specifically maintain a fork just for that instead of trying to push what are probably easy (but tedious) upstream fixes.
- poincaredisk 2y agoPurely guessing: abstracting a browser name is yet another abstraction layer. A later that is not needed by chromium. Maintainers of chromium primarily care about maintainability of chromium, not other forks.
- throwaway35023 2y agoIf the browser name is referenced in multiple places, it seems to me that by defining it in one place actually increases the maintainability.
- filcuk 2y agoI think what they're saying is that Chromium will remain Chromium, so maintainers have little incentive to worry about this