Capitalization bikeshedding! about rio

[snoyberg]

OK, I'll make a poll.

[mgsloan]

Framing seems good! I prefer camelcase for acronyms in general. Example mentioned by Taylor Fausuk elsewhere was XMLHTTPRequest. Gross! So the only consistent rule that works in all cases is camelcase even for acronyms. I suspect IO is the way it is because Io looks weird, whereas io looks fine.

It seems like to some extent we're getting into the space of "style guide". Maybe not how you should indent, but at least how you should name. So it makes sense to consider this as a question wider than the specific name choice for the rio's monad.

[snoyberg]

Argument for RIO to be upper case in the data type: it's simple ReaderT + IO, so the letters R, I, and O are already capitalized. Counterpoint: if io is both lowercase, it works.

Total aside: this bikeshedding around capitalization was one of the reasons pushing me towards using the jump name for this library instead of rio, see #8.

[akhra]

Tossing in a vote for Rio, though I won't be upset if it stays all-caps.

[mgsloan]

Should we put this up for a twitter vote? What's the process for making a decision? Concerned that if we let it languish, RIO will just become the defacto choice due to the cost of refactoring adopters.

It's ok but I will probably wince a little bit when I see it, at least until I get used to it. Seems rather shouty and harder to type, among the reasons already given.

[snoyberg]

https://twitter.com/snoyberg/status/958807583334248448

[roman]

Should this ticket be closed with final decission, or we want other data points besides the Twitter poll?

[snoyberg]

I'll refer the question to @mgsloan, since I think he's the strongest proponent of renaming. For the record, here are the poll results

[mgsloan]

Hmm, I think it's interesting that 51% or so are interested in change away from RIO. I don't like mixing RIO and Rio, it should be one or the other.

I wish that twitter polls would randomize the order so that there isn't bias based on the order.

However, since there doesn't seem to be much majority interest in changing to Rio / Rio, I suppose it seems reasonable to close this and I will just live with holding down shift for a few extra keys.

I do think that if one were to write down consistent readable naming rules, it makes the most sense to camelcase abbreviations. So, therefore Rio would be better if we ever want to write down such a rule.

[snoyberg]

OK, closing.