tsujp

Could you please elaborate, ideally in as much detail as you're comfortable sharing, on your Emacs and adjacent (org-mode, magit, any kind of syncing to your mobile phone with org-mode if that's done) workflow please. Often I find seeing people's real workflows (in detail and not wishy-washy) to be helpful since it gives me a concrete nucleus to crystallise off of... so to speak.

JS also has Crypto.getRandomValues()

The problem with the PGTK frontend is it is notoriously EXTREMELY slow. The latency on user input compared to the X11 (especially Lucid) version has some people reverting back to X11/Lucid.

When I do run Linux I run Wayland, I daily drive macOS, but better than both are what you already allude to: the Emacs widget toolkit which will focus on replacing the GUI frontend with SDL and also (equally potentially) introducing an actor-type framework (akin to BEAM's) for communication to decouple that GUI.

Understood, but in this (hypothetical) example his mother probably doesn't know exactly what angular velocity or torque are, so making things even simpler with a laymans "power" serves to get the point across.

One could include torque in the explanation to which the follow-up is probably "what's torque?".

The simpler one goes for that initial understanding, in most cases, the less technically correct one is; by design that helps the newbie learn and build up to a more technically correct understanding later on.

In general relying on excessive detail or jargon is symptomatic of not really understanding something when required to explain things in simple terms. I believe Richard Feynman said as much.

The general idea is people hide behind that detail/jargon precisely because they don't REALLY understand it enough to explain in simple terms what it is. That doesn't mean everything IS simple of course.

I assume you know now but in simple terms: the clutch connects the engine to the gearbox (transmission), so how well the clutch is engaged (connected) helps control speed. Gears multiply (increase or decrease) power from the engine depending on the gear you've selected.

I'll need to look into this but if anyone knows: is this available (easily) as a standalone package somewhere; think using the engine from a CLI without needing or contacting Google Sheets at all.

FINALLY!!

For 12 years visually vertically centreing text has required adding a padding or margin of a few pixels to the bottom or top, now (when adopted) it can be done properly.