29 karma · joined November 14, 2013
co-founder of https://accessiblesurveys.com
I could relate how he described the mathematical experience with what I feel is happening in my head/brain when I do programming.
- https://github.com/vaadin/web-components
- https://github.com/material-components/material-web (very, very sadly killed by google management)
Sometimes, I am wondering why it is not more widely used ...
Google, fool me once ...
For me, it has been a refreshing and profound way to reflect (and possibly better understand) on my own way to "think" (for instance when I build software architecture), and explore what might be happening in my head while doing so.
> since Material Web seemed to quickly end up in maintenance mode
This is really unfortunate to say the least - the engineering team has done a fantastic job there, but apparently no backing from Google despite the nice promise at the the launch of Material Web.
Not sure we are on the Perkins Database yet !
It is built on top of web-standard; I am surprised how (lit)tle attention it gets on HN (so far).
> 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.
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.
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)
Codebase is being migrated to Polymer 2.0, and better documentation.