[SU12 Beta] suggested small JS detail for the Hobbs gauge example

I think the SU12 sdk docs updates are great, documenting the html/css/js is a
very helpful addition and there are things in there I didn’t discover after
maybe 100,000 lines of MSFS html/js programming (like reading the panel.xml
info) My suggestion/idea is that the Hobbs gauge JS example assumes an update
frequency of every call to Update(), which is the easiest but as a default for
HTML/JS gauges is probably going to lead to a lot of inefficient code out
there. The Hobbs Gauge is super simple so it’s not as if that is going to
impact the sim but as a template for other gauges it’s missing the common code
that would control frequency of execution. If there’s a standardised method to
slow down those updates I’d recommend including that. Failing that what I use
in my code is to read (E:SIMULATION TIME, seconds) right at the top of my
update loop and only update if enough time has passed (i.e. I might have
this.sim_time_s = the latest simvar value and copy that to
this.sim_time_prev_s each time I update, and only update if
this.sim_time_prev_s is null or (this.sim_time_s - this.sim_time_prev_s) is
bigger than some time period. Whatever you put in the docs example is going to
be what devs follow for quite a while.

I’d like to piggyback on this, if only to highlight the question asked above:
“If there’s a standardised method to slow down those updates I’d recommend
including that.”
Is there a standard method that should be used?