@erniemiller @yaroslav it is called modularization, API surface is dictated by convenient usage, Ruby modules provide organization
-
-
Replying to @erniemiller
@fxn@yaroslav Would I be correct to say that Rails's opinion on organizing functionality is to prefer modules to collaborators?1 reply 0 retweets 0 likes -
Replying to @erniemiller
@erniemiller@yaroslav criteria is: usage drives API, modules or classes organize the code base internally1 reply 0 retweets 0 likes -
Replying to @erniemiller
@erniemiller@yaroslav if the implementation is a mess that's bad quality, the surface in absolute terms is not very meaningful for us2 replies 0 retweets 0 likes -
Replying to @fxn
@fxn@erniemiller@yaroslav You can't honestly be saying that the complexity (and surface) of an active record model isn't causing pain.2 replies 0 retweets 0 likes -
Replying to @sgrif
@sgrif@erniemiller@yaroslav in Ruby, modules allow you to organize the code, delineate bolcks of functionality, and offer a convenient API5 replies 0 retweets 0 likes -
Replying to @fxn
@fxn@erniemiller Also leads to surprising behavior: e.g. what happens if you do my_model.boolean_column = some_regexp.matchs(str)1 reply 0 retweets 0 likes -
Replying to @sgrif1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.