Skip to content
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

Consider choosing a new name #207

Open
ebkalderon opened this issue Aug 9, 2020 · 4 comments
Open

Consider choosing a new name #207

ebkalderon opened this issue Aug 9, 2020 · 4 comments
Labels
good first issue Good for newcomers question Further information is requested

Comments

@ebkalderon
Copy link
Owner

Most Tower-based libraries in recent times, if not all, have dropped the tower-* naming convention of older libraries in favor of catchier and more unique names. For example, see tower-web and tower-grpc (old) vs. warp and tonic (new).

Should we consider a similar rename as well? If so, what should it be? Or would getting downstream projects to migrate be too painful? Why or why not?

@ebkalderon ebkalderon added good first issue Good for newcomers question Further information is requested labels Aug 9, 2020
@ebkalderon
Copy link
Owner Author

Original suggestion from #206.

@Joakker
Copy link

Joakker commented Sep 6, 2021

How about beacon? Since beacons are used by ships to navigate the sea, and an lsp server is used to navigate through files

@davidhalter
Copy link

Simply for marketing reasons having lsp in there probably makes sense, just saying. I don't really care about the tower part.

@Joakker
Copy link

Joakker commented Sep 7, 2021

beacon-lsp really rolls off the tongue 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants