4 ms·
It’s just the kind of thing that happens in a huge, production codebase. There are plenty of reasons to be skeptical of Google, but some strings in multiple pl
by benreesman 2y ago
It’s just the kind of thing that happens in a huge, production codebase.
There are plenty of reasons to be skeptical of Google, but some strings in multiple places isn’t a good reason to be skeptical of the Chromium maintainers.
- KolmogorovComp 2y agoI 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
- deleted 2y ago[deleted]