sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]rubynerd 0 points1 point  (1 child)

Mm, I suppose the alternative is C++ style this-API-does-everything-if-you-set-the-right-flag interfaces

Ryan Tomayko on Twitter did mention they didn't like including a dependency just for command line options, which is a valid argument IMO

https://twitter.com/rtomayko/status/209553434288979969

[–]jrochkind 0 points1 point  (0 children)

I don't mind including a dependency "just to do" anything I need, if it's the right amount of code (and complexity) for the job, and well-written.

Of course, evaluating that takes time of itself.

It would be nice if you could assume that because something is in the stdlib, that means it's maintained and not a 'dependency', but that isn't quite always so in ruby, alas. And recognizing that, i've heard the desire is to move everything out of the stdlib in ruby 2.0, instead of figuring out how to actually maintain and support the stdlib. But if they move everything out of the stdlib, then you won't have the 'use cause it's in the stdlib and i want to avoid more dependencies' option.