lyinsteve

Specifically UITableView is a bad example here, because UITableView relies heavily on the `UITableViewDelegate` and `UITableViewDataSource`.

For that, though, you should make a separate class for the TableViewModel, to keep that code out of your ViewControllers.

If you check the press release, Simple is still considered a separate business entity and the Simple CEO is retaining his position. Apparently nothing will change.

Whoops, sorry, I meant 1, 4, 5, and 8. You're right about 2.

You're right. I'll update it to include both definitions in the morning.

Well, I think nobody uses them anymore because they aren't synthesized and the (readonly|readwrite) distinction is so clear.

-I've heard a lot about ReactiveCocoa recently, but I haven't had a chance to try it. Maybe I should. And maybe I will!

- I'm super guilty of just handling everything in AppDelegate (notifications, URI schemes, etc.) I need to work on this.

- CocoaPods are the greatest

You're right to an extent, but I don't think "Run your code through a formatter when you're done hacking it together" is a viable, maintainable, or scalable policy. Especially not for enterprise or team based workflows.

Also, #'s 1, 2, 4, and to a certain extent 8 are more questions of design pattern than 'style'.

I'm working on it!

I contribute to CocoaPods repositories, so I've seen a lot. I don't really feel adamantly one way or the other, but just be consistent.

You're correct. I've updated the post with credit to you, thanks!

This is a mostly STEM related site. It is well known that women are underrepresented in the STEM community. Further, the majority of college professors are men, but the majority of k-12 educators are women.

A different imbalance, and one to be considered, but separately from this issue.