status-im
/
re-frame-10x
mirror of https://github.com/status-im/re-frame-10x.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update README.md

This commit is contained in:
Mike Thompson 2018-02-10 18:43:12 +11:00 committed by GitHub
parent 1481e89012
commit 69b7d914fd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -38,16 +38,16 @@ what data is "happening".
So, data is at the core of `re-frame-trace` in both of the ways just described,
and that should not be the slightest bit surprising.
Think about it ... every single time you put a `printlin` into your program,
you are printing out what? And why? Data is the fuel of your investigation.
Each time you put a `println` into your program,
you are printing out what? And why? Data is the fuel of your debugging investigation.
Have you seen LightTable? It was attractive because it co-renders the data and
code. The shown data is the "paper trail" by which you can percieve the dynamics of the code.
Have you seen LightTable? It was attractive because it co-renders data and
code. The data presented is the "paper trail" by which you can percieve the dynamics of the code.
### It Is A Data Dashboard
Observing raw data is certaintly interesting, but it isn't enough. Data is the substrate and
we want to leverage it. Apart from anything else, there's often too much data - you
Observing raw data is certaintly interesting, but it isn't enough. Data is the substrate
we want to leverage. Apart from anything else, there's often too much data - you
can drown in the detail.
So, `re-frame-trace` tries to be a "dashboard" which curates this