When comparing Paths.js vs GraphicsJS, the Slant community recommends GraphicsJS for most people. In the question“What are the best JavaScript drawing libraries?” GraphicsJS is ranked 10th while Paths.js is ranked 21st. The most important reason people chose GraphicsJS is:
Not only Bezier curves but also any lines, shapes, arcs, etc. out-of-the-box.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Just helps building graphs, complements template engines or data-binding libraries
Can be used together with a template engine such as Mustache or Handlebars to display SVG graphics or instead of a static template engine, you can use a data binding or MVC/MV* library, such as Ractive.js, Angular, Mithril or Facebook React.
Pro 3 APIs for the price of one
3 APIs of increasing abstraction:
- Low-level (svg paths)
- Basic shapes (Polygon, Rectangle, Bezier, Sector, Connector etc..)
- Basic graphs (Pie, bar, stock, radar, tree, waterfall, sankey etc...)
There is no magic, you can have as much control as you want on how you define your graphs, source code very readable.
Pro Lightweight
18kb minified.
Pro Powerful line drawing
Not only Bezier curves but also any lines, shapes, arcs, etc. out-of-the-box.
Pro Convenient API
Clear and concise API with chaining support.
Pro Virtual DOM
Rapid drawing. Only what is necessary is drawn.
Pro Has its own transformation engine
No need to use embarrassing in-browser transformations.
Pro Legacy browser support
IE6+.
Pro Smart layering system
With z-index.
Pro Rich text features
Multiline text support, text measurement, wrap, indent, spacing, align, etc.
Pro Full accessibility (Section 508)
Pro Events support
All browser events are dispatched in the same way in virtual DOM structure also.