Miss Dada  🏳️‍⚧️

I love how in Ruby doing class DoesStuffService def call(x, y) # ... end end is good design but if you do def do_stuff(x, y) end you're a monster

Problem with second one is that it's adding the function to Object's instance_methods. So monkey patching + no namespacing. It's good for scripts, but iffy for apps and shouldn't be done in a lib. The first one actually has this problem, too, but it's added to Object's constants.

I think people probably prefer the first one because you can then namespace the rest of your constants within that one toplevel module/class, which you can't do with functions in Ruby. Anyway, my alternative of preference is `do_stuff = lambda { |x, y| }`

No way to expose that to other files though

Note: I'm not saying if you could that would be good. You're now in the C world of namespacing. But since we don't have any sort of scoped imports, we're already there. `http://Foo.do _bar` isn't meaningfully different from `foo_do_bar`.

There's no equivalent of `use foo::do_bar` that doesn't muck with some global state.

Check this out https://twitter.com/josh_cheek/status/1085646399880847360 …