Does this mean we have to get rid of Speechless at Google IO?

I'm really hoping somebody at Oculus/HTC/Microsoft sees this and wants to develop it, because I agree the hardware industry needs to step up its game to make this a reality.

Android Lead from Capital One SF here. I did and it was one of the best hires I ever made. He's the most enthusiastic and motivated person on my entire team, and is also amazing at UI and performance optimization. I've been begging them to send me more candidates ever since.

Did this get killed? I can't find it on the list

It fell in rank because users flagged it. Also, it set off the voting ring detector.

I failed pretty hard. 1/5

I don't have enough friends to even fail. 2/5 and then it alerted me I'd have to get more friends.

did you like the idea and exectution itself though?

If "most cases" means the average small team (2-3 developers), then you probably have a point. Once you have more than that, I think it's absolutely necessary to enforce code style in this way.

Thanks for reading the article so thoroughly.

Yeah this is the general idea we went with. We did our best to synchronize around it, but unfortunately we can never have total control, which necessarily introduces race conditions.

I would imagine this is what leads to the 0.4% crash rate I mentioned at the top of the article :-(

I was going for more of a sly joke with the title, but it appears to have not gone over well. I now regret my decision.

I agree. Would be nice to stop having to worry about this crap at every turn when developing on iOS.