6 ms·

We use ECharts in our open source BI tool (Evidence) and it's a great library. Has helped us build a declarative syntax for viz which can be version controlled

We use ECharts in our open source BI tool (Evidence) and it's a great library. Has helped us build a declarative syntax for viz which can be version controlled (https://evidence.dev https://evidence.dev) Previous HN discussion: https://news.ycombinator.com/item?id=35645464 https://news.ycombinator.com/item?id=35645464 (97 comments)

adeptima 3y ago
Looks great! Reminds me Obsidian DataView but with charts https://github.com/blacksmithgu/obsidian-dataview https://github.com/blacksmithgu/obsidian-dataview This whole ideas to have data, visualisations and knowledge base in one private offline place is very appealing
- hughess 3y ago
  We're fans of Obsidian! DataView looks cool - love the ability to define the tables in code inline in the markdown. That's similar to how we inline DuckDB WASM SQL queries in markdown: https://docs.evidence.dev/core-concepts/queries/ https://docs.evidence.dev/core-concepts/queries/
- archiewood 3y ago
  I love Obsidian. The Markdown <-> Markup typing experience is just so good compared to e.g. Slack, Reddit and other markdown-esque tools
meekaaku 3y ago
Evidence looks cool, and I evaluated sometime back. The docs says the pages are all pre-rendered for all possible combinations. Is that the case still? If so, if I have a date filter, is it going to pre-render all possible dates?
- hughess 3y ago
  We recently changed our architecture to include interactivity without having to pre-render all combinations. Pages are still pre-rendered with their initial content, but each Evidence app now ships with filter components and an in-browser DuckDB instance so you can build interactive apps. We call this Universal SQL - if you're interested, we wrote up our rationale for doing this here: https://evidence.dev/blog/why-we-built-usql/ https://evidence.dev/blog/why-we-built-usql/ Here's an example project with some filter components and custom styling: https://ecommerce.evidence.app/ https://ecommerce.evidence.app/ This is still a static app - the data warehouse was only hit during the app's build process

adeptima 3y ago

Looks great! Reminds me Obsidian DataView but with charts https://github.com/blacksmithgu/obsidian-dataview https://github.com/blacksmithgu/obsidian-dataview This whole ideas to have data, visualisations and knowledge base in one private offline place is very appealing

hughess 3y ago
We're fans of Obsidian! DataView looks cool - love the ability to define the tables in code inline in the markdown. That's similar to how we inline DuckDB WASM SQL queries in markdown: https://docs.evidence.dev/core-concepts/queries/ https://docs.evidence.dev/core-concepts/queries/
archiewood 3y ago
I love Obsidian. The Markdown <-> Markup typing experience is just so good compared to e.g. Slack, Reddit and other markdown-esque tools

meekaaku 3y ago

Evidence looks cool, and I evaluated sometime back. The docs says the pages are all pre-rendered for all possible combinations. Is that the case still? If so, if I have a date filter, is it going to pre-render all possible dates?

hughess 3y ago
We recently changed our architecture to include interactivity without having to pre-render all combinations. Pages are still pre-rendered with their initial content, but each Evidence app now ships with filter components and an in-browser DuckDB instance so you can build interactive apps. We call this Universal SQL - if you're interested, we wrote up our rationale for doing this here: https://evidence.dev/blog/why-we-built-usql/ https://evidence.dev/blog/why-we-built-usql/ Here's an example project with some filter components and custom styling: https://ecommerce.evidence.app/ https://ecommerce.evidence.app/ This is still a static app - the data warehouse was only hit during the app's build process