I sometimes watch "Ben Heck Hacks" live-streams rebuilding game controllers for people with disabilities [1]. People like him are what these files are for.
I've had quite a few constructive hobbies. I have built from metal and sold some parts, sculpt in clay or plastic and cast, and sold casts.
The point was not to sell them, but the community around the hobby.
I usually asked for only a little more than the cost of materials.
And that is also how I've approached open source software: It's a community first. In my first decade of using Linux, it was a movement. I got in it to build us a better future of computing, together.
I think Nokia's original Micro USB socket design had only two through-hole pins, which was not sturdy enough.
A standard USB-C socket has four: one in each corner like some later Micro USB sockets.
There even exists USB-C sockets with all through-hole pins but there's no space for USB 3 pins so they are all USB 2.0 or charging-only.
I used to buy cables with non-standard reversible Micro USB plugs, but I think there was only one manufacturer of them and now I can't find replacements.
Between Netscape Navigator and Firefox, their web browser was called simply "Mozilla". It supported GUI themes in XML with images which were officially called "Chrome".
Mozilla also hosted user-contributed themes on a web site called "Chrome Zone".
The browser was considered slow and bloated however, and when Firefox came, its lack of theme support was perceived as part of it having been de-bloated.
I might vaguely recall Mozilla being in an easter egg or alternate throbber in a Netscape browser, and my impression was that it had been an internal codename at Netscape which was then adopted for the open source project.
The range is 1..4096, so 4096 bits = 512 byte bitmap would suffice.
That is, if you're only ever going to test for membership in the set.
If you need metadata then ... You could store that in a packed array and use a population count of the bit-vector before the lookup bit as index into it.
For each word of bits, store the accumulated population count of the words before it to speed up lookup.
Modern CPU's are memory-bound so I don't think SIMD would help much over using 64-bit words. For 4096 bits / 64, that would be 64 additional bytes.
I sometimes use a trackball — without a "scroll wheel".
So in Google Maps on the web, I'd have to click the + and - buttons on the screen repeatedly to zoom in and out.
But those buttons don't always stay put. There is a status bar underneath it, that sometimes contains text so long that it wraps: and then that pushes the buttons up.
Fitt's Law does not just apply to screens but also to input devices.
That is why the keys on the outskirts of a keyboard are larger than other keys.
... except for the anorectic vertical Return keys on Apple keyboards with any European layout: which is a 1×1 key with a small vertical sliver.
Japanese "JIS" keyboard layout also has a vertical Return key, and Apple made that properly sized, however.
I've never had a Filco, but I remember it was significant in the early start of the keyboard hobby. Many mods had been tried on the Filco Majestouch first. The first custom key sets had been made for Filco's Majestouch layouts first, etc.
My daily driver at home for over a decade is a keyboard that I had built myself around community-designed replacement parts for the Filco Majestouch TKL.
This included a controller to customise the firmware, and that was my first start in programming microcontrollers.
1: https://www.youtube.com/@BenHeckHacks/streams
reply