2010
2009
Google Multivac- Lua Diff
- Moo Lobotomy
- Python JSON
- Stray Pixel
- Jupiter Photos
- Moon Photos
- Android Scope
- Impact Night
- Magnetic Noise
- DocEng 2009
- München
- Regensburg
- Java MobWrite
- Cursor Preservation
- Orbital Paper Airplane
- JSONP Memory Leak
- First Academic Paper
- Moore's Bet
- Moon Movie
- Hard Drive Crash
- Maker Faire 2009
- Self-collisions
- Mad Scientist
- Doorbell
- Rice DNA
- Somalia Affair
- Colorado River
- Great White North
- Lava Lamp
- Turbine
- Black and White
- CAT Triplet
- Dodecahedron
- MobWrite 3
- Differential Sync Talk
- 2008
- 2007
- 2006
- 2005
- 2004
- 2003
- 2002
Java MobWrite
25 August 2009
One of the criteria for something being a standard is that there must exist at least two independent interoperable implementations. For example, Microsoft's OOXML format[?] is not a standard, since only one application can open it properly (Microsoft Word). Whereas the HTML format[?] is a standard since there are several applications which can render HTML files properly (Gecko, Webkit, Opera, Lynx).
Thus it was important for MobWrite's growth as an interchange format for it to be reimplemented independently. For some time there have been two different servers: a daemon and an App Engine application. Now there are two clients: the original JavaScript client and the new Java implementation. MobWrite's demo page contains links to each of the clients, all talking with one another.
Quote from co-worker looking at some multi-coloured mapping functions on my whiteboard: "Every time I see something like that, I question whether I'm smart enough to work at Google." I looked at the incomprehensible spaghetti on his whiteboard and made the same comment to him. Everyone is an expert in their own domain.
