Comment by rui314
5 years ago
Author here. Haha, that's perhaps true. But at the same time, it seems like a tradition to give a silly name (e.g. "git") to a tool, and I actually like that name and the image to show that I'm not too serious. This is a fun project but not ready for production use.
Given the C was named because it was derived from B, I think there's an effective tradition in compsci of naming things by just playing with the letters.
M comes after G so the name tracks perfectly while also being weird and distinctive.
Sounds like you just need a multi-bump cake/jello mold like [1] with multiple "input spigots" pouring in with a "fast harden" aspect to have the perfect logo/name combo. Not sure how to convey rapid hardening with simple art, though... :-)
EDIT: You may just have to settle for speed/parallelism being conveyed by 2..3 spigots pouring in. :-) It's perfect - you can stay with moldy bread while it is a major work in progress and evolve to the more finished logo when your own work is "hardened" -- all without changing the name. ;-)
[1] https://www.foodandwine.com/cooking-techniques/baking/best-b...
> that name and the image to show that I'm not too serious. This is a fun project but not ready for production use.
I'm not sure if that image is the best way to communicate that status, given that the sudo sandwich logo exists (which coincidentally bears some resemblance to your moldy bread). A big bold "not ready for production" at the top of the README is probably a better way to achieve that.
The author has no such obligation, and "ready for production" is something that you would want to verify for yourself based on your evaluation of the project and your requirements.
Or it could be "bold".
Or “weld”.
Which I think might just be the greatest name for a new linker.
1 reply →