David Anthoff

I have to admit that I still hope that might be solvable in the vega/vega-lite code without us going through so many hoops. If not, then I guess we'll have...

I think there are two issues here that are quite independent: 1) if we have the data in the julia process already, we could be more efficient by not embedding...

Ok, I spent some time on this last week, but didn't get very far. I think the first problem I ran into was that the `browser` flag [here](https://github.com/vega/vega/blob/master/packages/vega/rollup.js#L50) affects _both_...

@jheer, would creating such a bundle that includes everything (i.e. including the file system loader) and uses the browser canvas be an option?

Yeah, that is annoying. I needs to be fixed upstream in vega-lite itself. I found this issue https://github.com/vega/vega-lite/issues/3911, not clear what the resolution there was.

I think in theory these should work in vega-lite as well: vega-lite specs are compiled into vega specs under the hood, and I would have assumed that one can therefore...

Yes, we should fix that! Did you find some vega-lite documentation that describes how dates and extent should be combined?

Hm, we should probably first figure out what the vega-lite story for `extent` and date time stuff is. It almost seems to me that they should just add native support...

> Unfortunately, current internal of VegaLite.jl does not allow this because it eagerly materializes the table. It'd be nice if the `data` property is untouched until the rendering time. That...

Ah, you're right, I still materialize the data at the beginning. I think mainly because there are many situations when a spec is turned into JSON multiple times right after...