{"action":"created","issue":{"url":"https://api.github.com/repos/hsivonen/encoding_rs/issues/4","repository_url":"https://api.github.com/repos/hsivonen/encoding_rs","labels_url":"https://api.github.com/repos/hsivonen/encoding_rs/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/hsivonen/encoding_rs/issues/4/comments","events_url":"https://api.github.com/repos/hsivonen/encoding_rs/issues/4/events","html_url":"https://github.com/hsivonen/encoding_rs/issues/4","id":198679562,"number":4,"title":"Consider renaming the crate","user":{"login":"nox","id":123095,"avatar_url":"https://avatars3.githubusercontent.com/u/123095?v=3","gravatar_id":"","url":"https://api.github.com/users/nox","html_url":"https://github.com/nox","followers_url":"https://api.github.com/users/nox/followers","following_url":"https://api.github.com/users/nox/following{/other_user}","gists_url":"https://api.github.com/users/nox/gists{/gist_id}","starred_url":"https://api.github.com/users/nox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nox/subscriptions","organizations_url":"https://api.github.com/users/nox/orgs","repos_url":"https://api.github.com/users/nox/repos","events_url":"https://api.github.com/users/nox/events{/privacy}","received_events_url":"https://api.github.com/users/nox/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-01-04T10:49:10Z","updated_at":"2017-05-09T06:36:14Z","closed_at":null,"body":"I really don't think having both `encoding` and `encoding_rs` actively maintained is a good idea at all, and there is nothing in `encoding_rs`' name that screams \"Gecko\" to me."},"comment":{"url":"https://api.github.com/repos/hsivonen/encoding_rs/issues/comments/300074499","html_url":"https://github.com/hsivonen/encoding_rs/issues/4#issuecomment-300074499","issue_url":"https://api.github.com/repos/hsivonen/encoding_rs/issues/4","id":300074499,"user":{"login":"hsivonen","id":478856,"avatar_url":"https://avatars2.githubusercontent.com/u/478856?v=3","gravatar_id":"","url":"https://api.github.com/users/hsivonen","html_url":"https://github.com/hsivonen","followers_url":"https://api.github.com/users/hsivonen/followers","following_url":"https://api.github.com/users/hsivonen/following{/other_user}","gists_url":"https://api.github.com/users/hsivonen/gists{/gist_id}","starred_url":"https://api.github.com/users/hsivonen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hsivonen/subscriptions","organizations_url":"https://api.github.com/users/hsivonen/orgs","repos_url":"https://api.github.com/users/hsivonen/repos","events_url":"https://api.github.com/users/hsivonen/events{/privacy}","received_events_url":"https://api.github.com/users/hsivonen/received_events","type":"User","site_admin":false},"created_at":"2017-05-09T06:36:14Z","updated_at":"2017-05-09T06:36:14Z","body":"I wanted to ponder this overnight before replying, but I deferred for too long. Sorry about the delay.\r\n\r\n> I really don't think having both `encoding` and `encoding_rs` actively maintained is a good idea at all\r\n\r\nWhile I understand the ecosystem concern of causing confusion by making people choose, I think it wouldn't be healthy for the Rust ecosystem for people to be discouraged from trying to write something better (on some relevant metric; in the case of `encoding_rs` suitability for use in a hybrid browser codebase of Rust and legacy C++). For that reason, I disagree with it not being a good idea for `encoding_rs` to be maintained.\r\n\r\nOn the other hand, it doesn't feel right to ask the crate that came before to stop being maintained just because someone felt the need to write something else.\r\n\r\nWe've covered before why it didn't make sense to develop `encoding_rs` as a stream of pull requests to `encoding`: The plan for `encoding_rs` was to redo both the API and the internals (for reasons _I_ think are good), and before it was up and running, there wasn't a credible way to establish if redoing both was a good thing, so how should the decision on whether to accept the first PRs have been made?\r\n\r\n> and there is nothing in `encoding_rs`' name that screams \"Gecko\" to me.\r\n\r\nThere is in the short description visible on crates.io. Also, I think it would have been a bad idea to over-constrain the scope of application by naming. (Furthermore, I don't like getting a request to rename something in order to scope it down relative to something else. It reminds me too much of the naming Stop Energy that the Encoding Standard itself got relative to the IANA registry.)\r\n\r\n> Consider renaming the crate\r\n...\r\n> I also think that there's an oversaturation of names such as &lt:noun>.rs, rs-&lt;noun>, etc. It would be nice to see some names that are more unique and not leveraging the fact that they are written in Rust as one of their sole defining features.\r\n\r\nI readily admit that the name is very unimaginative based on the fact that it's an implementation of the Encoding Standard. Back when I named the crate and even back when this issue was filed, I couldn't think of another good name, which, in retrospect, is laughably unimaginative. I can think of a potential other name now, but it, too, has the problem of how to refer to it outside the crates.io context without something verbose like \"the Rust &lt;noun> crate\". And I can think of a line of thought how the other name could cause confusion when contrasted with the `encoding` crate.\r\n\r\nBut more importantly, I'm now worried that bikeshedding the name even to something that would have been better had I used the other name to begin with would cause more confusion than it's worth considering that crates.io doesn't (AFAIK) have crate name redirects, that I've raised awareness of `encoding_rs` under the name `encoding_rs` for an extended period of time within Mozilla by now, and that even without formally announcing `encoding_rs` on users.rust-lang.org, there are already notable crates depending on it.\r\n\r\nThat is had I known what I now know back when I started, I'd have done things differently, but I'm not convinced that trying to change things now would be better than staying with the current name. Hard things in computer science and all that."}}
{"actor":{"display_login":"hsivonen"}}