Jayasimhan

Most of what you mentioned came from big companies with a $billion or more. Mike is an Investor. When he says that innovation is not happening, its probably because he is not seeing good ones starting up, i.e a new comer with an amazing idea. We'll see the effect a few years from now, when most great products come from Google/Amazon/Microsoft/Apple. It is probably that way already.

Every decade has had a game changer who came in from no where. Who is going to take away the 201x?

Ooh! I had the same idea about providing contextual information. But you executed on it. This is a wonderful tool that I'd use. All the best. Keep improving it.

i think he missed Gatekeeper.

ahh.. I see!

I think this is not true. Apple doesn't let you change icons on the home screen. Apps dont have that kind of control. Does it?

The blog doesn't give us a recipe to create the next big thing. It just explains the only way to make it.

Read as "Apple is 10 years behind Microsoft in our revenue growth chart."

Audiobooks & podcasts are my most used mode of learning. I generally take a walk while listening to the talk. Its a little exercise and learning at the same time. - Maintaining a regular route helps you focus. - make sure the entire route is safer

This whole Foxconn scrutiny is a blessing in disguise for Apple. How so?

Apple has deep pockets and very healthy margins that they could afford to fix this whole issue while keeping it in the media's radar and then at the right time turn it back to its competitors to prove their ethics. The competitors whose margins are already spread too thin will have great difficulty in coming clean in this issue. Apple gets a positive PR while others struggle.

What we can get out of this is post is that there is a lack of common protocol between the existing contributors and new ones who want to jump in. If TODO is not the right fit, then something like a FIXME or TESTME should help the new developer get started quickly. If a project follows this protocol, just add notes in the contribute section of the Readme; something like: "New contributors can get started with looking for FIXME in the code base".

Damn society, why can't you let these guys have a company blog where they can blog about this.