SebastianVerified account

@sebmck @Vjeux Yea. Referring to "keys to the kingdom". I agree with the "keys" part but not the "kingdom" part.

@sebmarkbage @vjeux i dont think itd be reasonable for that to happen to a proj like react.an example is iojs but node reunifc was necessary

@sebmck @Vjeux I'm reading this in a fork of WebKit which is a fork of KHTML. Most people didn't see that coming neither.

@sebmarkbage @vjeux nobody except browsers are building on top of something like webkit though so i don't see it being a useful analogy

@sebmck @Vjeux Feel free to pick a more appropriate example: https://en.wikipedia.org/wiki/List_of_software_forks … The point is, it happens all the time.

@sebmarkbage @vjeux i don't think forks that overtake their forkee are very common (or are they?)

@sebmck @Vjeux Not as common as the opposite but they are prevalent. There are also natural shifts of team members within a project.

@sebmck @Vjeux There is a natural aversion to forking since there is a huge cost. Inertia wins by default until forking is valuable enough.