Nice to see this done by hand. I do generally just defer to date-fns when I need to manipulate date-time logic though. Just depends on what you're doing.
I try to keep most app slices under 200kb for JS assets. With a shared library slices between 200k-500k.
For the most part I remove articles/projects tethered to commercial products. While it relies on a commercial piece of hardware, it's otherwise on topic and I find it interesting.
Given that I'm not aware of other products that support JS and Bluetooth, mostly curious what everyone else thinks.
Should the domain be blocked, or should I keep this site's content flowing?
With data attributes, any current browser supports the dataset property on the dom object... so e.target.dataset.id instead of e.target.getAttribute('data-id')
Other than that, the useCallback method is interresting at least.
I tend to prefer data attributes (dataset) because then it renders and is able to be utilized by ui/integration test frameworks.
Cool, hadn't dug into this, but seems interresting. Don't know that I'd use it outside of an appImage, unsure if there are packaging options, or FS limitations that are similar in Mac/Windows.
Are any of the dynamic/js based swf modules reasonable for this? I know it's not quite the same.