In early 2008, Wayne Shea and Tenni Theurer wrote a YUI Blog post on iPhone Cacheability in which they shared the results of research into various characteristics and limitations of Mobile Safari’s cache. Among other things, they found that individual components larger than 25KB were not cached, and that there was a maximum total cache size of between 475KB and 500KB.
Much has changed since then. We’ve seen two new major releases and many minor releases of the iPhone OS (now iOS), and several other mobile devices with highly capable browsers have appeared to challenge the iPhone. Stoyan Stefanov found, in late 2009, that the iPhone’s cache limits had changed (sadly, for the worse). But where do things stand now? And what about those non-iOS browsers?
Just… you know, putting this out there:
Starting an online interactive pornography firm where woman will use the iphone 4 to video chat with potential customers on a pay as you go basis. Hours are flexible, pay will increase as the business builds. Woman will receive a free iphone 4 to use as personal time when not working. Woman will talk to potential clients and chat with them and perform various acts as desired by clients. All information will be confidential.
Good stuff (ignore the dick waving):
Unless you ‘ve been living in a cave for the last year, you know that server side (better: ‘general purpose’) JavaScript is all the rage. Everything started with CommonJS: the emerging standard spawned an ecosystem of compatible implementations competing against each other while advancing the JavaScript state of the art.
Then, NodeJS happened: An async only JavaScript platform, powered by V8, not really interested in CommonJS conformance. RY (the new DHH) managed to grab the attention of the developer community with cool marketing, leaving other implementations in the shadows. One such great implementation that deserves more attention is RingoJS.
The contest format will be similar to Rails Rumble: Build any web project you can imagine; In 48 hours, starting from scratch; With a team of up to 4; Using node.js and whatever else you want.
Good stuff, I personally like mod_wsgi, but it’s cool to see how this stuff is evolving and how other people make things work:
A friend of mine, Kevin Whitaker, recently posted a great article about getting up and running with Django in a server environment for testing or production. He used Ubuntu, Postgres, Nginx, and FastCGI to make up his stack. I’ve never set up Nginx before, so his post was a great help in getting Nginx configured. My stack is slightly different, however, since I prefer to use Gunicorn instead of FastCGI and I use supervisord to manage my processes. I also use virtualenv to manage dependencies like Django itself and psycopg2.
SAFE FOR WORK: Clint’s white carrot (by 704 Race)


