The introduction of Swift pushed Objective-C into this weird state of still being the most popular language for iOS development, but one that is becoming less and less relevant with each passing day. Since Obj-C is not yet obsolete, we figured it’s a good time to talk about our technical interview process and what we expect from the candidates.
Some time ago I tackled the problem of messed-up connections in Quartz Composer. While the cable-like solution was surely an improvement in comparison to the original implementation, I quickly realised it can be easily made much better. Instead of making connections even more cabel-ly, I’ve attacked the core of the problem – the connections themselves.
I’m not a fan of the development cycle on iOS. The delays caused by recompilation and app launch are so frustrating that I try go through this tedious process as rarely as possible. Obviously, I still have to get some work done, so lately I’ve found myself using two tools indispensable in the course of making my life easier…
Frame is the king of layout. Everybody uses frames to position and resize their
CALayers. Throughout this post I’m going to focus my attention on
CALayer, as this is the underlying workhorse of
view.frame simply returns
view.layer.frame. Moreover, I will not discuss the
setFrame: setter. While the scope might seem very limited, it actually turns out there is a lot of fun stuff going on inside a plain, old