4 ms·

A bit sad that d3.js is not even mentioned here. To me it's a solid replacement for any MVC/MVVM framework. I guess it deserves its own category, maybe data mo

A bit sad that d3.js is not even mentioned here. To me it's a solid replacement for any MVC/MVVM framework. I guess it deserves its own category, maybe data model library?

jrumbut 8y ago
I think it's a real shame that D3 was never broadly recognized as such back when it first came out. I knew about it then, and made some small uses of it for SVG, but thought it was just an SVG generating library that could technically be used for HTML. I did a deep dive into D3 last year and it is amazing for generating HTML. I think in 2018 I prefer the model that React provides, but I didn't like approaches that required the sort of infrastructure React and Angular require back in ~2010. D3's use of vanilla javascript would have made it a top choice, and maybe would have promoted more D3 development.
- jordache 8y ago
  no built-in routing, DI, templating, components.. No it's a poor tool for what you are suggesting.
jordache 8y ago
huh? People using d3.js as a library for generic data binding UI? It's technically possible I guess, but the API, with its enter, update, delete paradigms, is very much data viz centric. Not the best option for a general front-end UI library.
- paraditedc 8y ago
  As a matter of fact, I use it to build web apps and it works pretty well: https://paradite.github.io/hn-ratio/ https://paradite.github.io/hn-ratio/ Source code (87 lines of JS): https://github.com/paradite/hn-ratio/blob/master/app.js https://github.com/paradite/hn-ratio/blob/master/app.js A sudoku solver I built with d3.js a few years ago: http://paradite.github.io/sudoku/ http://paradite.github.io/sudoku/ I think d3.js really striked a balance between raw jQuery/JS and full-featured React/Vue. I would recommend using it for building small-medium sized web apps with heavy data-centric UI.

4 ms·

A bit sad that d3.js is not even mentioned here. To me it's a solid replacement for any MVC/MVVM framework. I guess it deserves its own category, maybe data mo

by paraditedc 8y ago

A bit sad that d3.js is not even mentioned here. To me it's a solid replacement for any MVC/MVVM framework. I guess it deserves its own category, maybe data model library?

jrumbut 8y ago
I think it's a real shame that D3 was never broadly recognized as such back when it first came out. I knew about it then, and made some small uses of it for SVG, but thought it was just an SVG generating library that could technically be used for HTML. I did a deep dive into D3 last year and it is amazing for generating HTML. I think in 2018 I prefer the model that React provides, but I didn't like approaches that required the sort of infrastructure React and Angular require back in ~2010. D3's use of vanilla javascript would have made it a top choice, and maybe would have promoted more D3 development.
- jordache 8y ago
  no built-in routing, DI, templating, components.. No it's a poor tool for what you are suggesting.
jordache 8y ago
huh? People using d3.js as a library for generic data binding UI? It's technically possible I guess, but the API, with its enter, update, delete paradigms, is very much data viz centric. Not the best option for a general front-end UI library.
- paraditedc 8y ago
  As a matter of fact, I use it to build web apps and it works pretty well: https://paradite.github.io/hn-ratio/ https://paradite.github.io/hn-ratio/ Source code (87 lines of JS): https://github.com/paradite/hn-ratio/blob/master/app.js https://github.com/paradite/hn-ratio/blob/master/app.js A sudoku solver I built with d3.js a few years ago: http://paradite.github.io/sudoku/ http://paradite.github.io/sudoku/ I think d3.js really striked a balance between raw jQuery/JS and full-featured React/Vue. I would recommend using it for building small-medium sized web apps with heavy data-centric UI.