Well the core "issue" is they Vega ,as far as I understand it, isn't a format in the same sense as SVG is
So you're creating a hard dependency on having to embed a JS run time. There is no other rendering backend. If you have your problem space all speced out then maybe that's alright, but that generally leaves me a bit uncomfortable. The dependency graph is huge vs geom.
With geom I started my project with using batik, then moved to svgslamander when I needed to draw updates a bit faster and then when I had a bit more time to write my own renderer I changed to cljfx/javafx.
If I'm not happy with the vega renderer then I'm kinda stuck - while geom is all a digestible size
So you're creating a hard dependency on having to embed a JS run time. There is no other rendering backend. If you have your problem space all speced out then maybe that's alright, but that generally leaves me a bit uncomfortable. The dependency graph is huge vs geom.
With geom I started my project with using batik, then moved to svgslamander when I needed to draw updates a bit faster and then when I had a bit more time to write my own renderer I changed to cljfx/javafx.
If I'm not happy with the vega renderer then I'm kinda stuck - while geom is all a digestible size
The "renderer" as such is here
https://github.com/geokon-gh/corascope/blob/master/src/coras...
I basically massage geom's svg hiccup into cljfx maps. The formats are almost one to one