News for hackers. Stuff that matters.
Re:Dawn of kitchen sink libraries in Ruby by gnufied on Tuesday May 08, 2012 @10:00AM (#3943612)
Thats true, but often times a complicated library that makes these choices for you gets in your way, rather than helping the case.
Re:Dawn of kitchen sink libraries in Ruby by telent on Tuesday May 08, 2012 @10:09AM (#3943668)
Which is exactly why I'd rather use a library that doesn't make the choice of Rails and ActiveRecord for me.
Re:Dawn of kitchen sink libraries in Ruby by gnufied on Tuesday May 08, 2012 @10:23AM (#3943744)
Well, I tend to take a pragmatic approach about this. The question is, how much you want to deviate from convention of underlying framework when developing? 90% of Web applications out there, can reliably stick to rails conventions and they will be well served by it. But from my personal experience - handling file uploads, processing them is often very different from app to app. What we need is composaple modules not a single monolithic library that does everything and there lies my gripe.