I’d like to make it to NSCoder Night tonight, but I just have too much else to do today. Hopefully I’ll see everyone there next week!
CocoaHeads Silicon Valley at Apple on Thursday, May 15, 2008
The next CocoaHeads Silicon Valley meeting will be on Thursday, May 15, 2008 — that’s tonight! — at 7:30 in the Garage 1 meeting room at Infinite Loop 4 on Apple’s main campus. That’s inside and upstairs at Apple’s Infinite Loop campus in Cupertino. See the web site for directions.
This month’s main presentation is on the Best of Both Worlds — an introduction to Cocoa development by Scott Stevenson.
This talk is a combination of an introduction to Cocoa, as well as a series of advanced tips and tricks that even relatively experienced Mac programmers may not know about.
The idea here is that we want to give all of the people who are new to Mac and iPhone development a chance to get started, but we also want to do something special for our advanced programmers. So rather than choosing one, we’re just going to go ahead and do both.
Joel Norvell will also be presenting on how to edit PDF forms using Cocoa — he’s done a lot of work with PDFKit and Cocoa, and I’m looking forward to learning from him.
Thanks a ton to Scott Stevenson, Steve Zyszkiewicz, Michael Jurewitz and Joar Wingfors for organizing!
In general, at a CocoaHeads meeting we do some introductions, have a presentation including Q&A time with the presenter, and then have an open Q&A and demo-your-cool-app period. After the meeting there’s more independent mingling and discussion until it’s time to go at 9:30. Often a subset of the meeting moves to BJ’s Brewhouse in Cupertino, which is right in front of the Apple Infinite Loop campus on De Anza Boulevard.
Why is Twitter not just Jabber?
Twitter is a way to post a short message to a wide group of subscribers, and to receive messages posted by a wide group of subscribers.
That’s instant messaging. There’s already a standard protocol for it: Jabber (XMPP).
Why not just use it? Why invent a new protocol?!
Actually, Twitter already does have experimental XMPP access to the full timeline — rather than to individual timelines, or to your friends’ timelines — and you can use it to build things like TweetMaps and TweetClouds and Quotably and…
But Twitter should really be built entirely around XMPP. It shouldn’t be a web app at all, though it could certainly have a web front-end. In case you doubt me, here’s an example Twitter-like service implemented by Process One atop the ejabberd XMPP application server.