3 ms·
> a decade on you'll be able to determine which ones were the evergreens and had staying power while the rest will wilt and be forgotten. If only. A decade fro
by digi_owl 9y ago
> a decade on you'll be able to determine which ones were the evergreens and had staying power while the rest will wilt and be forgotten.
If only. A decade from now, many of the existing projects will have died not from code quality but from project maintainer churn.
This because the people that started the project to reimplement the old project has run out of features to implement, and thus is faced with the prospect of slowing down and fixing bugs. This to them is not fun, so they call out for someone to take over.
More often than not, the person taking over is barely interested in the current code, mostly there for the glory, and invariably ends up deciding unilaterally that the current code is unmaintainable and thus a full rewrite is in order.
- jacquesm 9y agoTrue, code quality is not the right measure but I wasn't really making that argument. Staying power also implies a lively community and one that can take over maintenance and further improvements once the original team stops working on the project. Any project that is still under 'original maintenance' is as far as I'm concerned a large uncertainty. One of the ones that I'm particularly worried about is the Linux kernel, if and when Linus gives up working on it there will be a period of some uncertainty.