The winner of the MDN Community Award 2009 has been announced. For now to find out who wins you need to listen to The MDN Show Episode 16. I will do a full write up of all the results and post them here next week.
Thanks to every one who voted…what a great community we have.
Scotty and John say a Happy New Year to all with this, the first MDN Show of 2010. This week it’s all about, “iPhone, iPhone, iPhone, everybody loves copy, cut and paste on the iPhone” and “GHUnit, GHUnit, GHUnit, everybody loves an open source unit testing framework”. Not sure what’s going on? Well all will become clear as Scotty and John lead us through another great show; reveal the winner of the first MDN Community Award; the lucky winner of a free place at this years NSConference and, give you not one, not two, but three opportunities to win an e-book from Pragmatic Programmers.
This free service for iPhone and Mac developers is based on the open source project CrashReporterDemo, which itself also includes other Open Source Software like PLCrashReporter.
When developing an iPhone or Mac OS X application there will always be bugs, and some of these bugs cause your app to crash. The earlier these problems can be identified, the better the stability of your app gets. When the app crashes the iPhone and Mac OS X will create a crash report file and these files are what the developer should be very interested in. Now for iPhone apps, Apple introduced a system which provides this data once the app is released. But there is always a time gap of days or weeks once that data is available for new releases, also beta releases cannot benefit from that. On Mac OS X these reports are also send to Apple, but there is currently no way to get them back.
This is where CrashReporterDemo and MacDevCrashReporter.com comes in. The project provides clients for iPhone apps and Mac OS X (currently in beta) which allows each developer to get these reports for any release and right away.
One of the dirty little secrets of the security industry is that a lot of the techniques in use today are not exactly new, in fact many can be traced back to the classical world. The use of ciphers to encrypt messages was employed by the Roman general, Julius Caesar, and of course the Trojan horse was known about during the time of Homer. Daedalus famously performed a risk assessment on the waxen wings he constructed for himself and Icarus to escape from exile on Crete, but due to user error (and in a neat demonstration of the problem with relying on customers reading security documentation) the wings still suffered from a catastrophic integrity failure.