3 ms·
I could not find in the post anything saying that they are going to abandon the current ESLint and let it rot while they write a new version from scratch. > I
by nine_k 4y ago
I could not find in the post anything saying that they are going to abandon the current ESLint and let it rot while they write a new version from scratch.
> I don't believe continually to make incremental changes will get us to where ESLint needs to go if it wants to be around in another ten years.
The scale of years for rewrite and migration seems right.
Rewriting from scratch may make plenty of sense. A completely new architecture should not be held back by any remnants of the old implementation. The old test suite is indispensable though, and the old sets of rules are an important source to consult (even if not to directly incorporate).
- WesolyKubeczek 4y ago> I could not find in the post anything saying that they are going to abandon the current ESLint and let it rot while they write a new version from scratch. One thing that stands out is that they haven’t grown twice the manpower with institutional knowledge overnight. You have to put a lot of effort into your rewrite, and you have to fix bugs in the existing thing.
- nine_k 4y agoThey can avoid building most new features in the old codebase (because they belong to the new codebase), and limit the work on the old codebase to bug-fixing. This looks realistic.
- NateEag 4y agoI wasn't worried about the team letting current ESLint rot- just about the possibility of the team sinking a bunch of time into architecture, planning, add starting from scratch that never really gets anywhere. I do see your point, though.