We just finished converting the old UI code to Google AppEngine, where the map can live on, for free, without the constraints of my cheap $15/mo shared hosting. It's running at the same URL as before -- campusmap.michaelkelly.org.
Some lessons learned:
- Online processing is for chumps. Disk space is really, really cheap. Like, unimaginably cheap. For any data that doesn't change, pre-calculate and serve up static content. The old version of CampusMap potentially did an online run of Dijkstra's algorithm (with some caching). The new version has all the path images pre-generated and *never* calculates them.
- Writing your own JS is for chumps. Use a framework. You really don't want to worry about whether your users are on IE or Safari or whatever, or if Firefox for OS X doesn't generate a keysym for the 'minus' key.
- Running stuff on your own server, unless you absolutely have to, is also for chumps. You don't want to worry about the version of your webserver or web framework, or whether the power went out in the one building where your server lives. Let someone like Google or Amazon do that for you so you can focus on the unique aspects of your app.