Paths.js
Languages and libraries
javascript graphics library
SHOW HN2014
How HN took it
5 positive, 3 neutral or asking, 1 mixed, 5 critical, out of 14 comments about the project. Thread score +0.04.
Docs: 1 for, 3 againstIdea: 2 for, 1 againstDesign: 1 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful, well-layered library that is easy to hack on
From 3 comments
This is a brilliantly conceived library. It does one thing well and even within that, decomposes into clear layers of abstraction. I've been using it at work and found the…
chrisdevereux on HNI guess you didn't make it more than a third of the way through the README. This looks super useful for the many circumstances where interpolating things into strings to generate…
bshimmin on HNHey, this is actually pretty useful. Thanks
ffn on HN
Helpful for avoiding string interpolation of SVG paths
From 2 comments
I guess you didn't make it more than a third of the way through the README. This looks super useful for the many circumstances where interpolating things into strings to generate…
bshimmin on HNYes, which is actually very useful once you start doing things like working with variables.
untog on HN
Objections
Docs need inline examples and images, too much text
From 2 comments
Your documentation needs images (or, you know, actual SVG).
imaginenore on HNI'm talking about the documentation examples, not the demo. They are simple enough to include the results right next.
imaginenore on HN
No explanation of differences from D3 in README
From 1 comment
You should have a section in your README discussing differences from D3. I've used D3 a little and understand some of the pain points. Looking at your library I'm asking myself…
mshark on HN
Demo written in CoffeeScript rather than plain JavaScript
From 1 comment
Looks nice, but I would really prefer the samples on the sample-site to be in plain Javascript. Coffescript isn't for everyone, on the web Javascript should be considered the…
josteink on HN
Requests
Add README section comparing with D3
From 1 comment
You should have a section in your README discussing differences from D3. I've used D3 a little and understand some of the pain points. Looking at your library I'm asking myself…
mshark on HN
Use CanvasPathMethods naming for compatibility
From 1 comment
This is OK, but it would be a lot more useful if the low level API used the standard names from CanvasPathMethods for compatibility with Canvas and Path2D:…
spb on HN
Add more chart features such as stacked bar charts
From 1 comment
This is a brilliantly conceived library. It does one thing well and even within that, decomposes into clear layers of abstraction. I've been using it at work and found the…
chrisdevereux on HN
Questions
Differences from D3
From 1 comment
Any core differences between Path.js and D3?
girinambari on HN
Memory leak behaviour over time
From 1 comment
Thanks! make sense. I have observed that lot of JS based SVG libraries having memory leaks and slowing down browser over the time, how paths.js behaves in this context?
girinambari on HN
Alternatives named
D3
From 2 comments
Any core differences between Path.js and D3?
girinambari on HNIf this is viable for making dataviz, it will be a great relief to get away from D3's disorganized mishmash of data wrangling and dom manipulation code!
woah on HN
High-level charting libraries built on d3
From 1 comment
This is a brilliantly conceived library. It does one thing well and even within that, decomposes into clear layers of abstraction. I've been using it at work and found the…
chrisdevereux on HN