8 Matching Annotations
  1. Nov 2019
    1. the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.
  2. Aug 2019
    1. With now more than 3000 modules, there are huge gaps in the quality of things you find in the npm registry. But more often than not, it's easy to find a module that is really close to what you need, except if it wasn't for that one bug or missing feature.
    1. The problem occurs when the maintainer of the package is too busy to merge my PR, so I'm just stuck with my fork.
    2. I often find myself in the situation where an npm package does exactly what I need, but has a bug or missing feature that blocks me from using it directly. So I fork it and make a pull request with what I need.