-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renaming #41
Comments
Hmmm personally I like the clarity that sourcekittendaemon is a wrapper around sourcekitten, although if it's likely that it's going to sever itself from the framework in the future perhaps now is a good time to rename. I've always been abbreviating sourcekittendaemon to just 'sourcekittend' though, so that might be another option? Loving the concept of Tiresias, not a big fan of the alternatives such as swiresias since it makes it obscure. It is a little hard to remember/type but given the end user almost never has to call the binary directly its not a big issue. Another thing to think about is what would happen to current and future editor integration names, I.e 'company-sourcekit' makes things pretty obvious but 'company-tiresias' may not be. Nathan Kot
|
When I created this, I quickly chose the first name that came to mind, completely ignoring the total lack of creativity here.
I think it would be good for the project to have a better sounding, shorter name. However, that's only my personal opinion here. Do others feel the same? Do you have a nice idea or suggestion for a fancy name?
My current proposal would be: "tiresias":
I find "understanding birdsong" a nice metaphor for what SourceKittenDaemon is doing. "Blind" is also a good fit as most of the work is happening in sourcekitten, and not here.
Or, alterations / combinations of that and "swift", i.e.:
"swias", "swiresias"
The text was updated successfully, but these errors were encountered: