<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Commentary</title>
<link>http://iphone.sys-con.com/</link>
<description>Latest articles from Commentary</description>
<copyright>Copyright 2008 iPHONE DEVELOPER&apos;S JOURNAL</copyright>
<lastBuildDate>Sat, 17 May 2008 08:26:00 GMT</lastBuildDate>
<generator>iPHONE DEVELOPER&apos;S JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>iPhone Developer Summit</title>
<guid isPermaLink="true">http://iphone.sys-con.com/read/519876.htm</guid><link>http://iphone.sys-con.com/read/519876.htm</link>
<pubDate>Thu, 20 Mar 2008 14:45:00 GMT</pubDate>
<description>This session will provide attendees with an overview of the iPhone SDK, including discussion of the App Store, Apple&apos;s planned distribution channel for SDK applications. Keep in mind that the contents of the SDK and experiences while using it are covered under NDA, so be prepared for me to talk in generics and leave out specific details that might be covered by the NDA. I am planning on providing a quick introduction to Objective-C for those attendees who may have never seen it and might be worried that it will be difficult to code in (it isn&apos;t!).</description>

</item><item>
<title>I Wish Sun Would Do More to Get Java on iPhone and Java 6 on Leopard</title>
<guid isPermaLink="true">http://iphone.sys-con.com/read/458945.htm</guid><link>http://iphone.sys-con.com/read/458945.htm</link>
<pubDate>Sat, 10 Nov 2007 10:45:00 GMT</pubDate>
<description>That leaves Java developers in a bad position. Java developers love the clean Unix-based Mac OS X environment for development. But we have been suffering with an unstable developer-only dont-run-this-in-production release of Java 6 for the past year. Mac OS X is now the getto for Java 6. I love Apple and Java. I wish Sun would do more to get Java on iPhone and Java 6 on Mac OS X.</description>

</item><item>
<title>How Has Open Source Helped or Hindered?</title>
<guid isPermaLink="true">http://iphone.sys-con.com/read/457350.htm</guid><link>http://iphone.sys-con.com/read/457350.htm</link>
<pubDate>Wed, 07 Nov 2007 13:45:00 GMT</pubDate>
<description>Open source provides an incredible amount of technical leverage for small companies. No matter who productive your rock-star programmers are and no matter how much judo you apply to your problems, solid infrastructure takes a long time and benefits immensely from broad involvement. It really does take a village to raise great infrastructure. The Ruby on Rails framework of today is a lot more productive than the one I was using before it was open sourced. I use features every day created by others, enjoy polish done by others, evade bugs caught by others. All work I would otherwise have to do myself. So I simply get more done for less effort than it would otherwise have taken. The same holds true for the other open source projects that have been cultivated in 37signals, like Prototype and Capistrano.</description>

</item><item>
<title>Building the Right Project Team</title>
<guid isPermaLink="true">http://iphone.sys-con.com/read/325132.htm</guid><link>http://iphone.sys-con.com/read/325132.htm</link>
<pubDate>Sat, 20 Jan 2007 11:00:00 GMT</pubDate>
<description>When building the right project team to complete a custom solution there are many forces at work. These include business drivers, technical drivers, and organizational and political motivations. Regardless of the business or organization there are three basic rules to follow in building a team to deliver a technical solution. The first is to involve the business before the team is even assembled. Each organization has certain technology standards that govern specific tools and products that can be used on a given project.</description>

</item></channel></rss>