Rename gem to bcrypt about bcrypt-ruby HOT 5 CLOSED

Using bcrypt as the name makes it harder for users to search for the project, documentation, etc. A better alternative might be bcrypt.rb

That said, I don't think there's a strong enough reason to rename the project given that so many people are already using it, have the name in their gemspec and Gemfile dependencies, etc.

from bcrypt-ruby.

I think the rename is a good idea, in order to fit the gem naming conventions more closely. As for searches, "bcrypt gem" already finds the project easily enough, and I'm sure "bcrypt ruby" would do just fine after the rename. "bcrypt.rb" seems to fall outside the gem naming convention anyway, and would probably just be confusing.

from bcrypt-ruby.

I think the biggest barrier is the fact that the current name is already in widespread use, and changing it would cause confusion and require many projects to update their dependencies.

from bcrypt-ruby.

Shouldn't let the past prohibit your future.

Why not create a brand new gem with the rename in place?

Dan

from bcrypt-ruby.

bcrypt-ruby could depend on the new gem. It would let others change, and have backwards support.

from bcrypt-ruby.