,
6 tweets,
10 min read
Read on Twitter
@capajj @andyhot @vuejs @Microsoft @typescript @ahejlsberg @drosenwasser You may think "open to any contribution from day 1" can only be a good thing, but for high visibility projects it simply doesn't work.
@capajj @andyhot @vuejs @Microsoft @typescript @ahejlsberg @drosenwasser First time contributions, especially during a phase where the design is still in flux, have extremely high communication cost. People can misunderstand the design, misuse internals, or introduce code that makes it harder to iterate in a different direction.
@capajj @andyhot @vuejs @Microsoft @typescript @ahejlsberg @drosenwasser Since I open sourced the 3.0 repo yesterday, I've reviewed over 20 PRs, merged maybe half, closing / requesting changes on the rest - which all require reasonable explanations. There went my Friday night and Saturday afternoon.
@capajj @andyhot @vuejs @Microsoft @typescript @ahejlsberg @drosenwasser Imagine doing this from day one. You won't be able to make reasonable progress before you burn out. That's why we have to do it in a controlled fashion, to limit the exposure in the early phases.
@capajj @andyhot @vuejs @Microsoft @typescript @ahejlsberg @drosenwasser We are also not open sourcing it only after everything is done. User affecting changes were discussed extensively in public RFCs. There's also still plenty of work left and open to contribution.
@capajj @andyhot @vuejs @Microsoft @typescript @ahejlsberg @drosenwasser Finally, the "inner circle" you mentioned didn't get that status because they are friends or family. They earned that early access by... guess what, contributing in the past, not just asking for it.
