I'm in a team that works on a pet prog lang for distributed systems, and we did some research of using an existing package managing systems. We've settled on NPM for now, but god I wish there would be a better generic package manager out there.
I also love eink. Maybe if there was a FOSS OS built around eink?
That's preposterous - I would be surprised if you get more than 5% of the power considering the losses in the transmitter, receiver (and related circuitry), not to mention the atmosphere itself plus whatever little bits get in the way (like, I don't know, the thousands of Starlink satellites and other space junk).
This should tell you something. Taking the time to name it nicely now costs almost nothing vs wasting your time trying to prove it can be refactored later and then doing that refactor later. Why? What are you getting out this? Taking 1 second to name it nicely vs the time it costs for everyone to listen to you "make a case for brevity", just please don't be that person. No one likes or respects that person more even when you are right.