square
Motion to archive
@RandomEtc @jasondavies @mbostock et. al
I'd like to motion to archive this repo. Seems like the perfect candidate since it has a successor org and is no longer maintained.
Would love your thoughts!
Speaking as one of the maintainers of the community fork, I would like to point out that, in all fairness, our fork has a different focus than the original.
It is more feature-heavy, and while the performance is still very good, we have made some trade-offs to support new features.
The original has a spare and minimal interface by design, while in the fork we have added most of the contributions we have received: simplicity is not as much of a goal for us.
I would argue that, whether this repo is maintained or archived, there is definitely still a place for the original crossfilter on npm, for those who prefer the minimal version.
Thanks for your input @gordonwoodhull! I will keep this in mind when writing the Archival readme. Luckily, an archived repo shouldn't interfere with people using the code much if they want to, in my mind it primarily makes it more clear what the expectation around updates is.