The place that low-level code like Istanbul occupies in the open source landscape makes it fascinating: its popularity is a long-term ramp and there’s little in terms of embellishment of the codebase: it’s all core.
It’s also a fascinating process to redesign open source projects. Contributions like this are almost done as Pull Requests on GitHub. Contributors, onlookers, and maintainers follow along with a set of changes and all of them can add to the long list of comments and suggestions that lead up to the final acceptance or rejection.
Design reviews on GitHub are quite different than code reviews: it’s much easier to review and react to a design than it is to read hundreds of lines of code change. There’s also aesthetic leeway in design and ‘one more change’ before it’s perfect.
The Istanbul redesign went really well: the comments were mainly constructive and descriptive enough to be implemented. Any time-worn design has elements that go against convention but fit some corner case, and this one has a few, like the lack of a width-limiter making it possible to see long filename paths in big projects.
Once you adopt Istanbul, you’ll use it hundreds of times: running and re-running tests to confirm that every branch and statement is covered. This redesign makes that experience just a bit more pleasant.