Bozhidar Batsov

> After 14 months, this issue has not attracted the attention of any maintainers, so I'm closing it. Thanks to everyone who provided feedback. I think if someone were to...

Just now. While I no longer remember the original reasoning I do recall it was a combination of several factors: - some of the points made by @kke - the...

> First, it adds zero cognitive load. Everyone knows what extend does (or should), everyone knows what self is within a Module (or should). module_function requires extra knowledge and having...

@jaredbeck > Is making them private the point? Yep, that was the point. :smile: As remarked earlier I didn't expect people would be including utility modules, as those are typically...

Again - I'll clarify the this guideline about `module_function` was always intended for the case of a module with functions (class methods) that are only meant to be used directly...

> I think that the rule about dsl methods and the absense of parenthesis should be removed from this guide, since what is or not a dsl method is highly...

I'm not arguing. Apart from class "macros" I use parens for pretty much everything myself. I was just saying that we can't have a community resource discourage a very common...

> Style/RescueStandardError isn't represented at all in the style guide I guess we'll have to change that and add a rule about it here. :-) > # good, if Style/RescueStandardError...

> TLDNR: The styleguide and RuboCop should always prefer the use of alias_method. If memory serves - it was like this in the beginning, but then someone complained that `alias`...

Seems this is why things got changed https://github.com/rubocop-hq/ruby-style-guide/issues/377 Probably the guide can be updated and everything on `alias` can just to go some sidebar for posterity's sake.