In this episode of the Stack Overflow podcast, Joel and Jeff sit down with Mac developer Daniel Jalkut of Red Sweater Software to discuss his experience as a longtime Mac developer and small Mac software business owner, and the possible impact of the iPad.
Daniel launched Red Sweater software way back in 1999 (and has been an active Mac developer since 1995), but it didn't become his primary business until 2005-ish. The big apps in his stable are MarsEdit, blog composing software, and Black Ink, a crossword app. There has been no iPhone version of these OSX apps to date because it wasn't a good fit, but the iPad is going to be a nearly perfect fit.
In Daniel's experience, the primary change in Apple's software developer support story over the last 15 years is that Apple has become much more pragmatic in adopting developer tools from the UNIX and open source world. Remember when Apple had its own unix, a/ux?
Apple has a whole new alternative to gcc, the clang compiler.
Joel agrees that the iPad will probably kill the Kindle hardware. We think e ink is kind of overrated. It's not clear how much this matters to Amazon. It is bizarre that the Kindle app will be allowed to run on the iPad as a competing "app store" next to iBooks.
I'm a little perplexed about the existence of iWork for the iPad, since it highlights the main weakness of the iPad -- while touch is great, the inclusion of keyboard support is odd, and I'm not sure how well it's going to scale to large screens and I think it's a weak replacement for the mouse paradigm.
Joel and I think Steve Jobs never really believed that computers made sense as general purpose devices. Computers should always have been appliances, and the iPhone and iPad are manifestations of that.
Steven Frank likens the iPad to the new world of computing, a bespoke from the ground up reconception of how computers should work, compared to the classic OSX, Linux, Windows desktop old world.
Is lack of support for Adobe's Flash on the iPad the equivalent of dropping the floppy drive from early iMac models? I'd say the floppy drive was already pretty useless by the time Apple dropped it, whereas Flash is still kind of useful in a lot of circumstances, as John Nack notes. Particularly on a large screen device billed as delivering a no-compromises web experience.
If Apple choosing to make a political statement about dropping Flash (on the iPhone and now iPad) results in websites built with better Flash fallbacks than an empty box on a web page, that is a good thing. It's just hard for me, personally, to accept that Apple is doing this out of the goodness of their own heart, rather than as a nakedly capitalistic way to protect the income stream from the App Store.
It has been pointed out to me that Stack Overflow is powered by bored programmers, so it is in our best interest for programmers to be bored at work.
Joel says that being bored says a lot more about a person's state of mind rather than whether the environment is actually boring. If you're bored while programming, "you are doing it wrong."
There are several dimensions to improving questions on any site on the trilogy; primary among those is editing (at 2k rep), and there always is voting to close (at 3k rep), flagging for moderator attention (at 15 rep). And meta-discussion about questions is always welcome on meta.stackoverflow.com.
Community moderation is an important part of our sites, and we're currently conducting an election to determine the next Stack Overflow moderator. You do need 200 reputation to have the right to vote, though.
For more great Mac dev discussion, check out Daniel's podcast with Manton Reece, Core Intuition.
We answered the following listener question on this podcast:
Jeffrey "How do you deal with programmers who are intellectually bored at work?"
Phil "I spend a fair amount of time on Server Fault, but I've seen a lot of new users not providing enough information for us to help them. As a result the signal to noise ratio has dropped. What can be done to improve this?"
If you'd like to submit a question to be answered in our next episode, record an audio file (90 seconds or less) and mail it to email@example.com. You can record a question using nothing but a telephone and a web browser. We also have a dedicated phone number you can call to leave audio questions at 646-826-3879.
The transcript wiki for this episode is available for public editing.