6 ms·
I feel bad for the Etherpad guys, who as I understand it, sold AppJet to Google to work on Google Wave: http://news.ycombinator.com/item?id=977015 http://news.y
by BobbyH 16y ago
I feel bad for the Etherpad guys, who as I understand it, sold AppJet to Google to work on Google Wave: http://news.ycombinator.com/item?id=977015 http://news.ycombinator.com/item?id=977015
- DTrejo 16y agoI still miss etherpad. I use some of the alternatives, but it's not the same :( alternatives: http://etherpad.org/etherpadsites.html http://etherpad.org/etherpadsites.html
- peregrine 16y agoGoogle docs is very similar to what etherpad used to be. All be it far less user friendly you can watch others edit and update in real time.
- param 16y agohttp://www.wsu.edu/~brians/errors/albeit.html http://www.wsu.edu/~brians/errors/albeit.html
- peregrine 16y agoThanks for pointing that out.
- jherdman 16y agoYes, you're right, but "albeit" is the word you're looking for, not "all be it".
- mjgoins 16y agohttp://en.wiktionary.org/w/index.php?title=albeit&oldid=9563626 http://en.wiktionary.org/w/index.php?title=albeit&oldid=...
- jherdman 16y agoInteresting, but dictionary.com and m-w.com claim that it's a contraction of "al(though) be it". * http://dictionary.reference.com/browse/albeit * http://www.merriam-webster.com/dictionary/albeit
- gruseom 16y agoIt's a mandatory contraction. You can't correctly write "all be it", just like you can't correctly write "where as".
- jeff18 16y agoThere's two main differences for me. a) It takes some work to create a new Google doc and set it up for sharing. Etherpad was as simple as pasting the URL. b) Etherpad shows changes from different users with a different background color. Google Docs is invisible.
- Twisol 16y agoGoogle Docs seems to support a very Etherpad-like interface, but it's a little too bloated for what I used to use Etherpad for.
- pjscott 16y agoA while ago Google Docs even switched to using Etherpad-style operational transformation instead of diff-match-patch. Some pretty mind-bending technology here: http://www.codecommit.com/blog/java/understanding-and-applying-operational-transformation http://www.codecommit.com/blog/java/understanding-and-applyi...
- deleted 16y ago[deleted]
- klochner 16y agoThey released the code, host your own (I have a friend who does): http://github.com/ether/pad/tarball/master http://github.com/ether/pad/tarball/master
- pgbovine 16y agowho as I understand it, sold AppJet to Google to work on Google Wave somehow i don't think they need your sympathies ... they probably got a decent amount of money from their acquisition, so they're probably not crying right now ;)
- callahad 16y agoCan money replace seeing your vision for realtime collaboration die twice? I'm sure they're not hurting, but if they were building the technology because they believed it could transform the way we interact with each other for the better... Well, that still has to sting.
- nl 16y agoThe Etherpad guys originally tried to build a platform (AppJet). Then etherpad took off, and they pivoted to building the company around that. Not saying they wouldn't be a bit disappointed, just that their original version changed at least once and they seem to have dealt with that ok.
- deleted 16y ago[deleted]
- mechanical_fish 16y agoCan money replace seeing your vision for realtime collaboration die twice? There is another way of looking at this. Let me rephrase that for you: Isn't it nice that Google gave us all that money in order to let us try our idea a second time? Just look at all the lessons we learned in preparation for the third time. Google may even open-source all our work so we can take it with us.
- dannyr 16y agoThey are probably working on something cool after wave. Maybe Google Me?
- jacoblyles 16y agoWhat's cooler: 1) a smallish hunk of cash 2) a thriving enterprise built around your vision for improving how people communicate The Etherpad sellout was, and is, the most disappointing acquisition I can remember.
- js4all 16y agoI agree and more sadly Wave in the form of Etherpad would have succeeded. A more de-centralized architecture with many Etherpad servers would have been perfect. Company related traffic wouldn't have left the LAN and of-site traffic would have been routed via federation protocol to other servers.