I was going to disagree with you about the boilerplate until I actually looked at the article, and you're right, it's just silly that the the Objective-C version gets about 10 additional methods that serve no real purpose.

The author must not be very experienced with iOS development because you can simply ignore all those extra empty methods if you do not wish to implement them.

It is really not fair to compare a verbose standard project template from Xcode with a a condensed Lua version.

It is only 'not fair' if the number of lines of code is important. Only the most naive programmers think that LOC actually means anything.

If you were really keen, you might consider which of the lines were authored by the programmer, and which were inserted by the tool 'auto-magically'.

In that case, Objective-C may actually come out ahead in this example!

Of course, I don't know how much of the Lua code was boilerplate supplied by the toolchain, all that stuff about twiddling the bounds and the frame might be boilerplate. In _that_ case, the actual amount of code written by both would be almost exactly the same.

And then we get onto secondary claims, e.g. benefits of garbage collection. (See the pretty graph)

Lastly we could compare them on 'prettiness' of code. Objective-C is quite ugly, but 'underscorising' the function names doesn't improve it much if at all.

-----

So overall everything is equal apart from the garbage collection/memory usage thing which tips the scales in Lua's favour.

Now, on iOS the speed can be a big issue, so knowing if there is a performance penalty that comes with that is a big deal, which I don't see covered in the article.

"""And then we get onto secondary claims, e.g. benefits of garbage collection. (See the pretty graph)"""

The pretty graphs are actually very misleading.

The graphs that drop down in the Lua version actually show the system load and not memory usage. So it shows nothing about garbage collection.

If you look at the process list in for the Objective-C version you can see that some other process, 'installd', is hogging most of the CPU.

I bet the author was syncing with iTunes or installing some software while running these tests.

What you can see in the Instruments screenshots is that the Lua version uses about 200KB more memory for the 'same' application.

Yes - it's pretty obvious that that CPU graph is not accurate.

> Only the most naive programmers think that LOC actually means anything.

Call me naive, then. Source code, even automatically generated, will be read, and may be modified. It does count. XCode template (unlike Yacc output) is source code.

> And then we get onto secondary claims, e.g. benefits of garbage collection. (See the pretty graph)

If I got it right, the little graph is about some aspects of runtime performance, which is secondary. But you sound like you don't acknowledge the primary claim of garbage collection: that it simplifies programs.

Except that Obj-C has pretty simple memory management. It's not like comparing with c or c++. More importantly Obj-C's system makes it easy to control when collection happens so you don't get pauses during inportant interactions. Does lua offer that?

I hardly know Objective C, so I'll have to speculate.

If you can control when collection happens and memory management is simple, then it's probably some kind of RAII. That makes sharing (shallow copies) unsafe, and ultimately encourages mutable state, which is bad[1].

If there's some reference counting going on, then GC pauses will occur whenever some giant data structure goes out of scope (and its destructor is called). That's predictable, but not obvious. Plus, a proper GC (generational and incremental) will not pause often nor long, if at all. Even then, many languages give you some control over the GC, giving you most predictability back. I don't know if Lua offers that, but I'd be surprised if it doesn't: it's used for games.

[1]: http://www.loup-vaillant.fr/articles/assignment

So you speculate despite not knowing either language or use case? Nevertheless I don't want to be a bad geek so I did some trivial googling:

http://stackoverflow.com/questions/4064451/luas-gc-and-realt...

tldr; LUA's GC isn't magic and for games you need to control it carefully. Even then a reference counting system is often better.

Answer excerpted:

As for the garbage collector. Use it as is first. If later you find performance issues use lua_gc to fine tune its behavior.

Some examples:

Disable the garbage collector during those times when the slow down would be a problem.

Leave the garbage collector disabled and only step it when game logic says you've got some head room on your FPS count. You could pre-tune the step size, or discover the optimal step size at runtime.

Disable the collector and perform full collection at stopping points, ie a load screen or cut scene or at turn change in a hot seat game.

You might also consider an alternative scripting language. Squirrel tries very hard to be a second generation Lua. It tries to keep all of Lua's good features, while ditching any of its design mistakes. One of the big differences between the two is squirrel uses reference counting instead of garbage collection. It turns out that reference counting can be a bit slower than garbage collection but it is very deterministic(AKA realtime).

Objective-C memory management has nothing to do with RAII.

No, it's naive to think that LOC means nothing — it might not be the most important metric for every situation, but given a reasonable definition, it certainly reflects something.

Otherwise, it would sound perfectly reasonable if I were to tell you, "OK, I'm going to give you a 500k LOC program to debug without tool support while I debug a 50 LOC one. First one to finish buys the other a car." You'd be naive to take that bet.

> Only the most naive programmers think that LOC actually means anything.

Sure but the author does actually compare a poorly written Objective-C version to an optimized (and different!) implementation in Lua and then goes on to say, hey look how much more pretty the Lua version is.

Then I must be a naive programmer.

If I can accomplish something in 1 line of code that takes me 100 lines of code in another language, that matters. It also probably indicates that the more succinct language has a higher level of abstraction.

"Now, on iOS the speed can be a big issue, so knowing if there is a performance penalty that comes with that is a big deal, which I don't see covered in the article."

I completely agree. Do you have some good suggestions on how to test this?

In that case, it is very weird that one sample (Lua) specifies the bounds of the UIWindow while the other is closer to the default setup and does not specify the bounds (Objective-C).