3 ms·
Wave's rollout was botched, its performance requirements were too ahead-of-their-time for 2009 hardware, and its UX (which didn't seem to "get" that sometimes y
by btown 9y ago
Wave's rollout was botched, its performance requirements were too ahead-of-their-time for 2009 hardware, and its UX (which didn't seem to "get" that sometimes you need to isolate your current work context from the global feed of activity in order to focus) was perplexing. But its legacy of helping to popularize Operational Transforms (and by extension, CRDTs) beyond academic circles did indeed live on - for instance, OT was adopted in Google Docs [0], and CRDTs were used in yesterday's release of Atom's real-time collaborative editing [1]. So in many ways, it accomplished exactly what to set out to do.
[0] https://drive.googleblog.com/2010/09/whats-different-about-new-google-docs.html https://drive.googleblog.com/2010/09/whats-different-about-n...
[1] http://blog.atom.io/2017/11/15/code-together-in-real-time-with-teletype-for-atom.html http://blog.atom.io/2017/11/15/code-together-in-real-time-wi...
- dkersten 9y ago> its performance requirements were too ahead-of-their-time for 2009 hardware For 2009 hardware running javascript in a browser, you mean? I was running much fancier native stuff much faster (including 3d games) on low-to-mid tier 2009 hardware. > So in many ways, it accomplished exactly what to set out to do. I think it definitely accomplished its goals technically, but it certainly failed on adoption. I personally never got into it. I tried it quite early and didn't like it. It was clunky and confusing and didn't seem very useful to me at the time. I wonder if it were re-created with slicker UX (and good performance), would I like it...