-
-
Replying to @sebmarkbage
@sebmarkbage@vjeux i think it's a good metric for who owns the keys to the kingdom. code dictates the docs, not the other way around.1 reply 0 retweets 1 like -
Replying to @sebmarkbage
@sebmck@Vjeux That's what open source is all about. The ability to dethrone, if the ruling few are no longer appropriate.1 reply 0 retweets 1 like -
Replying to @sebmarkbage
@sebmarkbage@vjeux i'm not sure what you're trying to say? are you referring to the possibility of forking?1 reply 0 retweets 0 likes -
Replying to @sebmarkbage
@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 necessary2 replies 0 retweets 0 likes -
Replying to @sebmarkbage
@sebmarkbage@vjeux nobody except browsers are building on top of something like webkit though so i don't see it being a useful analogy1 reply 0 retweets 0 likes -
Replying to @sebmck
@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.1 reply 0 retweets 2 likes
@sebmarkbage @vjeux i don't think forks that overtake their forkee are very common (or are they?)
-
-
Replying to @sebmarkbage
@sebmck@Vjeux There is a natural aversion to forking since there is a huge cost. Inertia wins by default until forking is valuable enough.2 replies 0 retweets 4 likes - 3 more replies
New conversation
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 