Laziness is a beautiful thing. Thanks to the non-existent motivation to do repetitive, boring and tedious tasks, we as a population grow and develop alternative ways to accomplish the same things, but in a new, more time efficient and productive manner. One such task is working with Core Image.
As many of you probably know by now, iPhone 6 Plus has a higher pixel density and now required @3x imagery to provide a crisp UI experience. I am big fan of dynamically drawing UI elements, button background, segment dividers, and many other elements in code. Let’s take a look at how we can make that happen.
Not long ago, when Swift was still in its infancy beta stages, I decided to run the two languages through some test side-by-side and see how they compared against one another when it came to speed of execution. You can find the article here. Time has come and Swift is officially released along with iOS 8 and its time to revisit the performance comparison.
After many evenings of fine-tuning and ironing out usability concerns, I’m finally proud to present my latest application – Map Calculator 2.0. It is now live on the App Store, and is available for download FREE this whole week (until August 11th, 2014)
An application that I’m currently working requires making the drop to the CoreFoundation level so out of curiosity I decided to contrast and compare the performance difference associated with using the Foundation-level
NSArray object versus its CoreFoundation counterpart –
CFArray. To be more precise, in this test we are exploring the performance difference of iterating over the mutable version of both objects, inserting a string, getting the array count (to replicate a real-world scenario where the array size is not given) and retrieving the element at index. This is a brutally simple test, but will hopefully provide at least some insight into how fast each method really is in comparison.
I use these objective-c macros in every single project I work on and I highly recommend you use them too. These macros are designed to simplify your code, make it easier to read and maintain. Include them in your
ProjectName-Prefix.pch file to make the complete set available to the entire project.