search

artsy / mobile

Mobile Team TODO
http://www.objc.io/issues/22-scale/artsy/
84 stars 11 forks source link

Blog about open source library selection process #46

Closed dskatz22 closed 8 years ago

dskatz22 commented 8 years ago

What considerations are made, test coverage, community support, pretty README, code quality etc.

orta commented 8 years ago

Interesting, given that I created the CocoaPods quality indexes, they contain the sum of what I believe, but I'd be open for someone else to take a look at this.

ashfurrow commented 8 years ago

As a product of working with Orta, my criteria match his closely.

I'm fairly liberal in adding dependencies – I'd much rather use something someone else has written for a variety of reasons. Maybe those reasons would make a good post?

orta commented 8 years ago

We expanded a bit of that on our objc.io

There is a tendency, particularly in iOS developer communities, to eschew third-party dependencies. Developers fall victim to “Not Invented Here” syndrome and end up wasting valuable hours of development time tackling the same problems others have already solved for them. On our mobile team, we vehemently reject NIH syndrome and instead favor the philosophy of “Proudly Discovered Elsewhere” (a phrase we appropriated from another developer, naturally).

Good examples where we had space to do NIH: NAMapView, FBSnapshots & Expecta/Specta.

orta commented 8 years ago

Linked to #49

orta commented 8 years ago

I did this!