Live data from Hacker News

Launch HN: Evidence (YC S21) – Web framework for data analysts

news.ycombinator.com

51–60 of 94 posts

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#52
It's great how naturally the charts and data are integrated into Evidence reports. I spent today trying to accomplish a similar style in a Metabase dashboard and was largely unsuccessful due to the limited text controls and layout options.

SQLite support would be nice!

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#54

I like it. I've seen the same issue and agree people over index on no code. I didn't see it on your page, do you get into visualization as well?

Thanks so much! Yes, definitely. We include a visualization library with the Evidence. You can write to add a line chart to your document, for a histogram etc. You can see the documentation for the chart types we have built under 'components' in our docs. Here's the histogram: https://docs.evidence.dev/components/hist Designing this is one of the trickiest parts of the project, and is going to be one of the biggest a…

Have you looked into using Vega-Lite? It’s declarative and configurable.

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#55
congrats on launching and building atop SvelteKit!

Since you have some data processing inline with your Markdown, I am wondering if you explored using MdSvex? https://mdsvex.pngwn.io/

it would seem like it would be a pure win for you as you (your users) get reusable functions, on-document styles, local component state, and so on.

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#56
I have been doing this in emacs org mode for years i.e. reading from database and plotting the results along with documentation in single org file which is version controlled using git, how is this different? I can also export to html and share with others. something like this

#+begin_src emacs-lisp (require 'ob-sqlite) #+end_src

#+RESULTS: : ob-sqlite

* Headline 1

* Headline 2 #+begin_src sqlite :db users.db :colnames yes select * from users where id > 1 limit 10 #+end_src

#+plot: set:"xlabel 'id'" set:"ylabel 'N'"

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#57
In my experience, most reporting has to be done as printable PDF or it doesn't exist. There doesn't seem to be a good story for paginated media yet. In the past I've used polyfills for CSS pagination features to generate modestly well formatted PDF documents. Then you can either print it out from the browser or use a headless browser to do the same. Also there are modules on NPM for Latex-style typesetting.

This looks very promising, also with the inclusion of svelte. I'd have to see how well it integrates with Python and R, as far as I can see you'd need to export data from those to make it usable, which is probably easy as well.

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#58

I have been doing this in emacs org mode for years i.e. reading from database and plotting the results along with documentation in single org file which is version controlled using git, how is this different? I can also export to html and share with others. something like this #+begin_src emacs-lisp (require 'ob-sqlite) #+end_src #+RESULTS: : ob-sqlite * Headline 1 * Headline 2 #+begin_src sqlite :db users.db :colnam…

This looks already way more complicated than "Evidence".

OP wrote that people have been doing similar things for a long time. They are aiming to standardize and polish this approach.

Re: Launch HN: Evidence (YC S21) – Web framework for data analysts

#59
> In our experience, the BI layer is the weakest part of the modern data stack. The BI layer has a poor developer experience, and decision makers don’t really like the outputs they get. It turns out, these two issues are closely related. The drag and drop experience is so slow and low-leverage that the only way to get all the content on the page is to push a lot of cognitive load onto the end user: global filters, drill down modals, grids of charts without context. Like most users, business people hate that shit. And because the production process isn’t in code, the outputs are hard to version control and test—so dashboards break, results are internally inconsistent, and so on, in just the way that software would suck if you didn’t version control and test it.

If I could upvote this a 100 times, I would. I've felt this pain everyday with Looker, Mode, Metabase, every other BI tool that I've tried.

Post reply on HN