@thomasnield Here is my position:
I like a lot D3.js but I found it difficult to use and understand.There are a lot of chained function calls that are not easy to apprehend: you don’t know at what depth you are. The experiments we made to wrap d3.js from kotlin were not satisfying. The transformations from a statically type system to a dynamic one is not easy to handle. In d3.js you usually have array of array, where in kotlin you have generic list of classes.
Having d3.js inside nashorm and wrapping calls with kotlin seems overcomplicated to me.