Metrics to compare against

[anvaka]

List of metrics:

1. License
2. GitHub popularity: Number of followers/forks/bugs/commits/recent activity
3. Rendering engines: WebGL/SVG/Canvas/etc.
4. Platforms: NodeJS, Browsers
5. Performance: Graph size vs FPS
6. Supported layout algorithms
7. Library size

What else?

[josdejong]

Here some more ideas:

• Feature richness, flexibility
• Styling options (can you easily style it to match your websites layout)
• Ease of use, learning curve, required skills
• Dynamic/static rendering (static drawing or a dynamic graph where you can move/zoom around)
• Supported data formats (JSON, DOT, ...)
• Editable or view-only (dynamic/static data)
• Platforms: NodeJS, Browser, Mobile devices (Extension to your no. 4)

[anvaka]

Very nice! One more: Memory usage comparison.

[maxkfranz]

(1) Perhaps under platforms, you may also want to include supported package managers and require() environments -- e.g. CommonJS, AMD.

(2) Measurements of memory and FPS seem like a nice idea, but in practice those measurements won't be useful unless you provide jsperfs. A manual measurement is not practical to keep uptodate.

(3) Points like "ease of use" are subjective and qualitative so perhaps best belong in a text review section outside of a table of metrics. "Easy", "medium", and "hard" probably aren't very useful in a comparison matrix.

[anvaka]

Added information about average "issue closed" time. Check it out: http://anvaka.github.io/graph-drawing-libraries/#/all

This information is based on https://github.com/hstove/issue_stats