1,019 karma · joined November 2, 2010
Wow, interesting words from someone who works in finance.
With an entirely separate article on women: http://www.nytimes.com/2014/12/14/upshot/us-employment-women...
Don't assume the worst!
https://github.com/facebook/componentkit/blob/master/Compone...
GCD is fantastic—one of my absolute favorites. We're trying to solve a problem one level above that: exposing an API that doesn't require every view developer to know the details of managing GCD queues and updating a UICollectionView.
As for Autolayout, it's very powerful but isn't performant enough for layouts as complex as Facebook's News Feed. We tried it first before developing ComponentKit.
To me (an American), that sentence seems incredibly lenient.
"only"? n.b.: If your business model is renting out luxury condos to people on the Internet, you're going to have a bad time. People will use them for parties.
Plus, who would really enjoy working in a workplace where everyone doesn't care? I couldn't stand it even if I were paid more, couldn't lose my job, and had more vacation time.
What's more he doesn't propose eliminating federal aid or loan guarantees, he advocates letting you discharge student loan debt in bankruptcy and putting colleges on the hook for some percentage of that default.
Sounds like a great idea to me. Schools that equip their students for well-paying jobs have nothing to fear, but diploma mills out for easy loan money will suffer.
I'm not sure how they did that (#define?) but stay far, far away. Imagine if you opened up a Ruby codebase and found out I had aliased NO to be the same as the language builtin false... yeesh.
Also, setting boolean instance variables to NO in init is silly since Obj-C objects are calloc'd, so all ivars are guaranteed to start with default values (nil/0/NO).
For native apps in frameworks like Cocoa Touch of course it's an entirely different ballgame. A view controller has quite a bit of state, usually some different modes, maybe some enforced state transitions. So the controller pattern makes a lot of sense there.
The author is spot on about how some architectural oddities like one-method-classes come from Java's lack of functions as first class objects.
http://www.tuaw.com/2012/02/06/siri-may-be-iphone-4s-only-be...
The fact that Apple supported iOS 6 on the 3GS is proof that they're pretty serious about backwards compatibility.
That's not to say income inequality isn't a problem, but misleading charts are the wrong way to make an argument.
Monkey patching is fragile, but in tests, who cares? If it breaks, you see why and you fix it. Tests don't have to be held to the same level of reliability as production code.