Skip to content

Conversation

@sferik
Copy link
Contributor

@sferik sferik commented Dec 18, 2013

It makes sense for this repository to be named yajl-ruby, to avoid ambiguity with other wrapper libraries (not to mention YAJL itself) but the gem name need not include -ruby, since the rubygems package manager is tightly coupled to the Ruby language. Just as the sqlite3-ruby gem was renamed to sqlite, this package’s name should just be yajl.

This also increases consistency between the library’s name and the way it is required.

require 'yajl'

@brianmario
Copy link
Owner

I've been thinking about this lately as well. It's come up many times in the past I just wasn't sure how best to handle it other than just shipping the changed name :)

@sferik
Copy link
Contributor Author

sferik commented Dec 18, 2013

I’ve proposed a similar change to libxml-ruby and fleshed out my thoughts on how best to roll this out: xml4r/libxml-ruby#81 (comment).

Just as I offered to libxml-ruby, I’m happy to help coordinate this release process.

@sferik
Copy link
Contributor Author

sferik commented Feb 21, 2014

For what it’s worth, bcrypt just made this transition seamlessly. Is there any reason not to move forward with this?

@padde
Copy link

padde commented Jun 19, 2014

👍 I always try to gem install yail when I realize it’s called yajl with a J – oh no wait yajl-ruby 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants