4 ms·
>and contributing to Chromium as a non-Googler is notoriously difficult. so fork?
by nova22033 8y ago
>and contributing to Chromium as a non-Googler is notoriously difficult.
so fork?
- takluyver 8y agoForking a big, fast moving, security critical piece of software like a browser is totally impractical unless you have a sizable company behind you to maintain it.
- lallysingh 8y agoIt's probably easier to just keep a set of diffs.
- takluyver 8y agoEven maintaining a patch against a rapidly changing codebase takes work, and then you've got to make builds. This is why people contribute changes upstream rather than everyone maintaining their own modified version of every application and library.
- icebraining 8y agoSo what? Lots of things are impractical for individuals.
- guiolo 8y agoIt's not just individuals. If people can't contribute to the project it is hard to build or maintain knowledge about that technology so another party can use it at all. Sharing code that few people de facto can use shouldn't give you much credit, or at least not as much as the alternative. Unless it is, as someone suggested, about signaling.
- scrollaway 8y ago[edit: Moved here: https://news.ycombinator.com/item?id=16994356 https://news.ycombinator.com/item?id=16994356]