the problem with technical software names is that they are either too long, too pointless, do not die when underlying tool goes through re-incarnation(looking at you angular) or worse, too important to be wasted on a lesser quality project (looking at you react-router).

in my company, we have a tool whose technical name was four word long, and has just as much cognitive load as any technical name.

one of my biggest contribution to that project was to Name it.i gave it a simple name, with zero relation to tech or any software

and suddenly our PMs, Managers, Users can pronounce it and can actually type it correctly and of course recall it's name flawlessly.

so, at least from my experience, having a small, easy to pronounce name is more important than having technical name.

Moreover having a name with all of the qualities is definitely desirable, but there are many projects in world and not that great names. and many Great names (looking at you, Vue.js) are either already taken or beyond my naming skills