You should, there's lots of vanity sizing nonsense going on. For example, a 3sixteen ST-100x in size 30 is actually a 31 inch waist, and it will stretch about another inch!
Well, when TF2 came out, it was laser focused. Every class had a role, and was strong and weak against certain other classes. So now, you throw a bunch of new items, and it loses that. The sniper is weak to spies, that's how it's supposed to be. So then the sniper gets given a shield that makes spies unable to stab him, and a jar that he can throw on the ground and reveal them. Engineers were weak to snipers, but now they can take control of their sentries and manually shoot things outside of the normal range. So the end result is that everything ends up becoming pretty okay against everything. I haven't played the game for a long time so I don't remember everything.
The other issue, which is one of the reasons I stopped playing (aside from me pretty much stopping playing video games in general) is aesthetic overload. I don't like the notion of things being called "purely cosmetic" because appearances have meanings. The 9 classes were designed to be recognizable from their silhouettes alone, which is pretty brilliant. But now you can pile an absurd number of things onto your character, completely changing that. Not only do you not know what your opponent is equipped with anymore, you also have an additional psychological blocker to identifying them. And it's just tacky. TF2 was originally a 60s spy movie parody, and I really felt that. Now it's just... everything. It's just a lot less compelling to me.
I am a little skeptical of the platform portability. A high quality application has a lot of UI code. Then, if you're Doing It Right, on iOS, you're probably going to use Core Data and/or iCloud for backend storage. For networking, you need to manage the activity indicator, etc.
So it seems like there are two choices:
1. There's a wrapper library on top of UIKit instead of straight bindings. Not good, more levels of junk, and can't really provide access to the entirety of the API since it doesn't 100% match with Android.
2. It's platform portable... as long as you don't actually use any system frameworks. In that case, it could be nice for games, I guess, but would it be fast enough?
What's the point of Cocoapods instead of just using a submodule? Git already has a native way to handle subprojects, and adding an extra external dependency and gitignoring the results (I guess) feels dirty.
I use the retina MBP at "1920x1200", which wasn't available on any 15" MacBook previously. I do wish this was the "native" resolution though. "1440x900" is comically large.
The Facebook Camera app still hasn't been updated for the iPhone 5. Too bad, because it's an incredible app, much nicer than Instagram (which isn't horrible or anything).
What's with the categories? They don't seem to be used in either of the primary .m files (cmd+f "mtl"), so they aren't really needed. Do one thing well.
If you want to make a higher order function library, that's fine, but I don't see what it has to do with mapping data to JSON, and I don't think that users of the library should have to get a bunch of modifications to the standard container classes to get the nice model class. Why not split it into two libraries?
I decided to uninstall Messenger, I like being able to chat while browsing other Facebook pages.