How to write an iOS app purely in C

Great work for trying it though. Are all those bytes actually needed? E.g. I see a lot of "restore VFP/Advanced SIMD registers" when you don't seem to be using those at all. It would be interesting to see how much you can cut out, as currently it looks more like a mostly mechanical ObjC -> C -> Asm translation, like a compiler would do, instead of a human. As a point of reference, on Win32 an app that just shows a window with some text in it requires <1KB of binary.

It sounds like you're arguing against learning. When you're a beginner, one of the most frustrating things is when people won't answer your questions due to an air of superiority. I know you feel like you're guiding people onto the best path, but it can't be true that you're correct in every case. So it must be true that at least some of the time you're being deliberately evasive for incorrect reasons. In other words, you believe you're being helpful, but you're not.

Answer their question, choose not to answer, suggest an alternate way of doing something, but please don't go on for hours about why their original plan is a bad idea. It's often the quickest way to kill the fun and their will to learn.

I've personally have wrestled with this, and many times its a case where its most certainly a premature optimization. There are times where I've bent over backwards to avoid calling a `new` inside a Java loop because of some project, some years ago, was running slowly and when I profiled it came down to too many allocations in a loop. I try to hammer "benchmark & profile" in may head however.

In general, Boost is just a huge library. Using it may make your code unfamiliar to people who don't know the whole huge library, because there is a strong temptation to start using random parts of the library. Additionally, the style of Boost doesn't always mesh well with the coding style you are using. This is why Google, for example, bans boost except for a small number of approved functions.

When I'm on Stack Overflow, I always end up downvoting a lot of answers that don't answer the question being asked. "You are dumb for wanting to know the answer to this question," no matter how politely it's phrased, is not an answer.

(Actually, it appears Objective-C is certainly older than the CD-ROM and is from about the same era as the audio CD.)

As a multi-decade PHP developer, I would have guessed you'd be used to people deriding your language of choice and, based on that experience, developed enough common sense to not make a fool of yourself so publicly. I guess I expect too much of people.

I can just imagine $AAPL shareholders quivering. "What is this guy talking about?"

Betting it all on Objective-C, a unknown language based on a superseded language. Steve was so ballsy. Google at least had a clue. Java + Android actually makes sense.