Indeed, lit is fantastic.

It is built on top of web-standard; I am surprised how (lit)tle attention it gets on HN (so far).

I experienced the same. The overall dev experience / responsiveness of pakage management makes it very unlikely I would like to go back to npm ever.

> developer burden imposed by needing to denormalize information.

> Then the other pain point is the "joins" use case;

We usually do that client side, with the aid of a web-component holding a ref to the (realtime db, not firestore) database path, and rendering its value. The payload is small as you only fetch data you use.

That works pretty well, even with long lists or grids; quotas/price on the realtime db are pretty generous.

Shameful plug here - and yes dc.js is great! An alternative web-component based approach to dc.js is available here: https://github.com/PolymerEl/multi-verse. It is still based on Polymer 2.0, migration to lit-element in the way.

"in the way" (interfering or obstructing) -> "on the way" (forthcoming / can be expected)

i->o is a common typo; here it could be negating the intended meaning!

I recall seeing your project almost 2 years ago. A bit of unsolicited advice - It would really help if your Github and docs page linked to a few actual interactive examples showcasing the different chart types supported, and the general capabilities of your library. Screenshots really don't do justice to projects like dc.js and your lib that hinge on interactions between users and charts/data.

It also appears that your demo for multi-chart is:

1. Broken

2. Blocked by most browsers and requires manual override of security suggestions (probably related to https and some sort of cross-domain things going on).

I'd be curious to see any working examples like the one dc.js has on it's main doc page. Cheers

Thanks a lot for your advice! Live demo used to be working on webcomponents.org - one service powering them has stopped working...

I launched this approx 2 years ago - using it in prod, but not had proper time to devote on better doc/demo/presentation. Looking forward to it during current migration to lit-element.

Awesome. Sounds good. Best of luck! I know that it's hard to find time for any of this stuff when it's all a labor of love in your free time.

This is already a start: https://www.webcomponents.org/

Shameless plug for a data + markup based approach, hiding some of d3.js complexity: https://github.com/PolymerEl/multi-verse.

Codebase is being migrated to Polymer 2.0, and better documentation.

Looks great! Can we think of a way to integrate muze using your approach? :)

Core idea behind this approach is to expose API properties as web-component attributes so that you can compose your charts and visualization at markup level (and share/react to properties between components).

I do not see any reason why this could not work with your API. If interested, some concrete/simpler examples available from https://github.com/PolymerEl/multi-chart (also being ported / simplified; ETA next week)

Humbly tried a polymer/webcomponents approach for composing similar vizualisation than dc.js. it uses d3v4 and multi-chart (https://www.webcomponents.org/element/PolymerEl/multi-chart) as a charting library: https://www.webcomponents.org/element/PolymerEl/multi-verse