# Value of ActiveSupport's Modularization

**URL:** <https://www.ruby-forum.com/t/value-of-activesupports-modularization/68430>\
**Category:** Ruby\
**Created:** [September 12, 2006, 5:09pm UTC](https://www.ruby-forum.com/t/value-of-activesupports-modularization/68430 "2006-09-12T17:09:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trans](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/dfb087/32.png) [@Trans](https://www.ruby-forum.com/u/Trans)\
**Post date:** [September 12, 2006, 5:09pm UTC](https://www.ruby-forum.com/t/value-of-activesupports-modularization/68430/1 "2006-09-12T17:09:15Z")

</div>

Curious about this. Can anyone cite a _practical_ benefit of  
ActiveSupport’s modularization of it’s extensions? What I mean by  
pratical is a use other than just “cool, see they are all in modules”.  
To be sure you know what I’m talking about here is ActiveSupports Hash  
extension:

class Hash  
include ActiveSupport::CoreExtensions:#️⃣:Keys  
include ActiveSupport::CoreExtensions:#️⃣:IndifferentAccess  
include ActiveSupport::CoreExtensions:#️⃣:ReverseMerge  
include ActiveSupport::CoreExtensions:#️⃣:Conversions  
include ActiveSupport::CoreExtensions:#️⃣:Diff  
end

Thanks,  
T.