he lesson for future games might be this: make your technology extremely simple, easy to modify, ship it with a diverse enough pool of content that people can extend it to create a variety of settings and styles, and promote the sharing of this content as a way to add value to your game.
When designing your first REST system there are a variety of mistakes people often make. I want to summarize them so that you can avoid them.
[I actually liked the fried chicken at the Highball. Let's go get fried chicken!]
Why Mario wears a mustache and more!
Turns your iPhone/iPod touch into a numeric keypad for your notebook.
Sorta like a couch except smaller and outside, also, a client side JSON document store. Perfect for webkit mobile apps that need a lightweight, simple and elegant persistence solution.
Built with typographic standards in mind, Baseline makes it easy to develop a website with a pleasing grid and good typography.
How to use Image Magick
Google makes a move to put Opera at #5.
Jacob linked to this, now I will; you will find it more useful than I did.
Matthew Congrove took some time to play with the iPhone SDK, but it wasn't his bag, so he decided to go back to building a Web application for the iPhone, and was pleasantly surprised with the updates to Safari that enabled new things:
But in the blogosphere-to-come, everyone should put themselves out there 100%, linking everything they like, and subscribing only to those feeds that match their own tastes best. The idea that BoingBoing has won the status of an 'indie NewYorkTimes' makes
[I like this more than Minus Garfield]