3,589 karma · joined December 8, 2009
The socket.io codebase has been shrunk dramatically, and it's as a result easier to scale/maintain.
We recently made the Socket.IO parser 300% faster. The new underlying websocket server is extremely fast (check the benchmarks at https://github.com/learnboost/websocket.io/), and optimizations to long-polling are coming as well.
http://www.quirksmode.org/blog/archives/2009/04/google_spons...
SubEthaEdit (while incredibly impressive and producer of a big technical feat at the time), is a _plain text_ collaborative editor.
Similarly, but higher up the scale, is Etherpad, which has the concepts of annotations for rich text.
On Google Docs and Google Wave, I can collaborate on rich text of arbitrary markup. For example, I can import any Word document and collaborate on it in real time. This is not a huge challenge from just the convergence / intention preservation algorithms perspective, but because they run on a browser. Wave went to the extent of normalizing the HTML representation of the `contenteditable` divs across all browsers to enable converging document results. Google Docs ditched `contenteditable` and rewrote an editor on top of plain HTML, with range selection logic and caret simulation built from scratch.
The fact that software like iWork Pages / MS Word[1] don't offer similar functionality (even with native, hand-made rendering engines and no browser support challenges) in 2011 speaks of Google's clear superiority in the office suite cloud offerings, which is the point the original article was trying to make.
[1] There's a plugin for Word http://www.codoxware.com/ that enables OT written by one of the most well-known OT researchers, who spoke at Google in '08 (http://www.youtube.com/watch?v=84zqbXUQIHc)
It's possible that log.io is not trying to send absolutely every message (which is the reason I introduced the volatile flag for the upcoming version: https://github.com/learnboost/socket.io-node/tree/develop)
1) One line to install
npm install socket.io
2) Three lines two use on the server
var io = require('socket.io');
var socket = io.listen(yourHttpServerInstance);
socket.on('connection', function(conn){ conn.on('message', function(msg){ console.log('message from client', msg); }); }
3) Three lines to use on the client
<script src="/socket.io/socket.js"></script> <!-- assuming node serves the HTML too -->
var socket = new io.Socket().connect();
socket.send('my message!');
* examining the docs
* taking care of error handling
* coming up with an easy to use developer interface
* keeping it updated if the API calls were to change
every time you need translation.
You're also implying it's better than having a package that can potentially abstract many different translations API, that you can just add as a submodule of your git repository, and use with one `require()` call away.
I disagree.
I'm no IE hater, but it's pretty evident for any serious programmer that IE8 is simply a patched-up IE6.