Add obstacle for monkey-patching

[jodosha]

@rosenfeld Hi there and welcome!

@rosenfeld

Would you be interested in creating such a ruby-web-developers group that wouldn’t be tied to Rails or ActiveSupport?

Absolutely. Which tool for communication you were thinking of?

@rosenfeld

I mentioned that as one of the strongest reasons why I switched to Roda last week in two articles:

http://rosenfeld.herokuapp.com/en/articles/ruby-rails/2017-05-01-feeling-alone-in-the-ruby-community-and-replacing-rails-with-roda
http://rosenfeld.herokuapp.com/en/articles/ruby-rails/2017-05-03-ruby-on-rails-the-bad-and-good-parts

This is my attempt on stopping feeling alone in the Ruby community. I want a stronger Ruby community that has other values than the Rails community.

I read the “feeling alone” last week when somebody shared it on Reddit. A great read

@rosenfeld

I’m not sure if you noticed but the last release of the mail gem will also patch Ruby core classes.

Yes I spotted it long time ago: Remove monkey-patching? · Issue #936 · mikel/mail · GitHub
But we kept mail because it’s a solid lib, we didn’t wanted to implement a lib from scratch just because of monkey-patching. Of course I’m extremely happy they removed it from the lib.