> What are the things that D3 did right to get the acclaim, and why does it keep it for so long?
As a dev, what D3 did right for me is kept the code stable, provided clear sample code for most use-cases, the internet (thanks folks) made lots of runnable examples available via blocks and jsfiddle, maintained precise documentation (even for older versions in github as markdown files) and has almost no external dependencies (so my local .js+.html files from 3 years ago still work without needing any broken npm install or jspm install)
Moving from v3 to v4 was not as painful as I thought it would be.
Once I got over the core concepts of selections and enter/update/exit cycles it has been a breeze and a pleasure to work with.
Thanks Mike and everyone else who's made reasonable and sensible choices for D3 !
As a dev, what D3 did right for me is kept the code stable, provided clear sample code for most use-cases, the internet (thanks folks) made lots of runnable examples available via blocks and jsfiddle, maintained precise documentation (even for older versions in github as markdown files) and has almost no external dependencies (so my local .js+.html files from 3 years ago still work without needing any broken npm install or jspm install)
Moving from v3 to v4 was not as painful as I thought it would be.
Once I got over the core concepts of selections and enter/update/exit cycles it has been a breeze and a pleasure to work with.
Thanks Mike and everyone else who's made reasonable and sensible choices for D3 !