I'm a fan of naming things correctly.
I loathe Devise.
I just can't bring myself to read Enumerable source.
Why is that?!
TL;DR
Stop na...
For further actions, you may consider blocking this person and/or reporting abuse
I actually like the
Somethingableconvention of naming modules, because for me it is natural to think of modules in terms of what they allow the including object to do.I do however dislike trying to name modules according to the
Somethingablepattern, but I wonder if that's just a failure of my vocabulary.Awarableis very clunky, though. Is the point that when included in an object, you can... make that object aware of something? Off the top of my head, I would have gone withAlertable,Notifiableor something. Something that, even if you don't like the naming convention, is actually recognisable as a word.I'd like to think that the ruby community is a very friendly one where we don't call other people's concepts or naming schemes "**** stupid". But that's just my humble opinion.
Besides that, it's not the module that's enumerable, instead, by including
Enumerablethe class becomes enumerable. The module, due to its nature, isn't capable of doing anything on its own, only inside a class it gives power to the class.Like I said, I haven't read the source, but taken at the face value of the name
include Enumerationwould absolutely be more understandable thaninclude Enumerable.