metatation

> actually implemented in-depth testing beyond the anemic xcode support

I think this is the key motivator for people looking at alternative architectures. My guess is most people wouldn't stray very far from basic UIKIt/MVC if the established practices weren't so hard to unit test.

I see the experimentation with alternative approaches as the iOS community going through a phase of maturity, and is a positive signal. Many people in the community care deeply about issues of code quality and testability and while striving for simplicity. The increase in iOS architecture related articles is an indication of unrest and an active search for better practices. I suspect that it is only through these experiments that we will discover the balance we are looking for.

Similarly, I think articles like the OP are a healthy resistance against the pendulum swinging too far the other way. Although I agree with several points made I'm disappointed that testability isn't even mentioned and thus many points ring hollow.

Except that rotten tomatoes are not green..they are deeper red in color than a fresh one. Plus, why throw tomatoes at all if you like a performance. For me it's a completely broken analogy.

Maybe it's just me, but I find the "Tomatometer score" to be confusing. The combination of the tomato graphic with a number confuses an otherwise obvious rating.

I have a very strong (but false) intuition that the tomato graphic is a qualifier for the rating number. i.e. "Is this saying that 92% of people would throw tomatoes at this performance? Oh it's a fresh tomato...but wait, why would they throw tomatoes if they like it. Oh I see, the tomato is a lame representation of the rating, not saying something about the rating number."

Anyway, my false intuition is so strong that I still have to concentrate to ignore the tomato and simply look at the number (even if the number itself is controversial as noted by this discussion thread).

I took a stab at this exact scenario years ago (1999?) and came to roughly the same conclusion. I ultimately decided to treat it as a travelling salesman problem where the distances between nodes (people) were weighted based on how recently they had matched with each node in the past.

This ultimately led me to create a TSP solving library that implemented a bunch of the known heuristic algorithms to approximate the solution. Worked out pretty well in the end and learned lots while I was at it.