Purely guessing: abstracting a browser name is yet another abstraction layer. A ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		poincaredisk 11 months ago \| parent \| context \| favorite \| on: Fixing a bug in Google Chrome as a first-time cont... Purely 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 11 months ago [–]

If the browser name is referenced in multiple places, it seems to me that by defining it in one place actually increases the maintainability.

filcuk 11 months ago | [–]

I think what they're saying is that Chromium will remain Chromium, so maintainers have little incentive to worry about this

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact