Physicist, Senior Developer and IT Consultant, University Lecturer, Freelancer and Startup Founder
Most recent activity
I know Discourse from Node-RED and can definitely agree.
However, AFAIK, Gordon wanted to avoid having to maintain a forum himself, which is why he looked at GitHub Discussions...
I don't think so
If you change intervals seldomly,
setInterval may consume a little less power - but compared to what you need for drawing your screen contents, you should never be able to recognize the difference.
do not mix both approaches! Either use
setTimeout as shown above or start a new
setInterval whenever your drawing period changes:
var TimerId = setInterval(draw,1000)
TimerId = setInterval(draw,60000)
I usually prefer a construction like
var Interval = 1000;
}, Interval - (Date.now() % Interval));
- (calculation and) drawing may take longer than 1000ms (should be
Interval may change dynamically (e.g. depending on screen lock)
But, most often, a simple
setInterval should be sufficient.
I don't think you should judge your user's opinions just by the posts in this topic.
To use myself as an example: being critical (e.g., in terms of privacy and GDPR compliance) does not necessarily means "dissent" - it's just that I want to avoid running into troubles by not having looked at the consequences of this switch.
On the other side: since I am participating in a GitHub discussion (on the new GitHub "achievement" badges), I definitely prefer the existing forum!
that's indeed an interesting finding, but I doubt that it would have a significant effect on performance:
computeDiffusion does a lot of computations and rounds in the end only - replacing it by
+ 0.5 and relying on internal truncation and clamping would probably not be faster but less intuitive. However, rounding (of small values) is important for the final display any may therefore not just be omitted completely
computeHeating does not have any noticeable effect on the overall speed (it deals with 16 pixels only, not 256)
prepareDisplay rounds indices into an array only - and this cannot be omitted as you may easily test yourself
var Test = [0,1];
undefined rather than
Anyway, thanks for your effort!
@Gordon @ChrisS I don't want to discuss any GDPR issues of Windows or other Microsoft products here - the question should instead be: will the migration to GitHub discussions (which should lower the load on Gordon's shoulders) be safe for users (and Gordon himself!)?
Right now, it seems so (from the viewpoint of a non-lawyer, of course)
Yes, GitHub was bought by Microsoft (sigh!) but they officially(!) claim to be GDPR-compliant (and seem to offer the data processor contracts Gordon may need to be safe himself). For me as an end-user, this claim is sufficient - any further inspection should be left to lawyers.
As a consequence, I'd now welcome the migration to GitHub discussions (although I still don't really like the idea that anybody would need to register with GitHub just in order to join a discussion about Espruino - at least, "foreigners" should be able to read what was written in the forum)
From GitHub's Data Protection Agreement, the following excerpt seems promising to me
To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR.