Clojurians Log v2

@dustingetz feature request: “volume-knob” control for insta-editor’s and auto-transact’s edit-eval delay - http://alexandrkozyrev.hyperfiddle.net/:volume-knob/

the best example I have is http://alexandrkozyrev.hyperfiddle.net/:change-on-mouse-move/

if you play with “pure html” on-mouse-move - https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_onmousemove - you will notice that you probably don’t recognize all points, it just too fast

mouse is a “motory” function and I want it to stay unconscious, so 200ms inertia, or stroboscope effect is good enough

in other words, browser can capture every point of mouse pointer but I can’t really process more that one point every 200ms

back to http://alexandrkozyrev.hyperfiddle.net/:change-on-mouse-move/

For this specific example - Datomic won't ever be able to keep up with transactions that fast, you would need to integrate a different database for realtime data

here are two examples: auto-transact is off and is on

that’s the point, for my workflow - 2sec inertia is a good pace

Can you store the temporary values in an atom and only transact/stage when you intend to store it in datomic?

I’d like to be able to tell HF - transact these values every 2sec (or 1 sec)

Are you trying to query all that data? even at one per second, its still going to blow out the datomic indexes

yes, the history, the track wont be as accurate in Datomic as in Ratom, these will be less points

“all data” or what and how much will be important later to read from database is way to context dependent

at the moment I think that 20sec of 1sec points (i.e. 20 points) is a good enough aproximation

WHat if you use :db/add instead of :db.fn/cas, so it will only save the latest one until you transact (this would work with the staging area)

probably 2mins at 0.5 sec step (120 points) is my own limit

yes, :db/add - my “volume knob” intent is to be able to play a bit with transact delay, I guess 0ms delay is just a DDoS attack on Datomic, and lower pace will be sufficient

The staging area can handle getting slammed, it just can't go through the transactor

Well, the staging area can handle a casual typing pace

Tell me if you think this will work:

for the insta editors, instead of a volume knob, we're going to have alt-enter be like "save and run"

it will also save after 10 seconds of no typing, or something like that