I was psyched when I first read the subject, since I figured they'd be lending Google Docs their awesome text editor. Instead they're going to Google Wave, where the interface blows. Etherpad's lightyears more useful, more flexible, and more valuable. Blah.
The Etherpads themselves were very impressed with what the Wave guys showed them, and they are the best qualified to judge this sort of technology of all the hackers I know. Maybe some of the stuff they saw was unreleased, but whatever it was was, the Etherpads liked it, and they seem genuinely excited to work on it.
It seems understandable that both buyers and sellers are pleased with the transaction, after all, they both agreed to it. It doesn't really address the OP's (however direct) 'that sucks' comment.
Any early-adopter of a start-up product accepts the risk that the company behind the product might be unsuccessful. Customers like that bet, in part, on the notion that despite the statistically long odds, the company is making every conceivable effort to stay alive and succeed.
The 'buyout-and-the-product-dies'-type exit introduces a sort of divided loyalty and misalignment between the goals of the founders and the goals of their customers - if you're unsuccessful you might fail and we might suffer an abrupt service termination but at the same time, if you're quite successful, we might also suffer an abrupt service termination.
If only they had interviewed at Google and joined the team they wanted to be on a year ago.
These transactions trade on the goodwill of early adopters. And they make it harder for other startups as potential early adopters start to assume that it's better to wait for what Google releases instead of investing time in a product that will be scrapped either if the company fails or is successful and acquired.
Most of the Etherpads are ex-employees of Google that left to start their own company. I don't see any other way to interpret your comment except that you are suggesting that they should've quit running AppJet a year ago (since the option to be bought didn't seem to be available then) and interviewed at Google to get their jobs back to work on GWave at an early stage, but without the added benefit of having millions of dollars worth of Google stock. This seems quite bizarre.
My point is that if they wanted to build their own company they should remain committed to the product they built, and find a better support model for current customers/users than shutting down without notice.
I do not begrudge them making money at all. But one reason that they have "millions of dollars worth of Google stock" is because they offered a service that people adopted and paid for. I think they have more of an obligation to customers and users than the initial announcement indicated and I worry that not taking better care of customers in the transition makes it hard for other startups.
Agreed. When Google Wave first came out part of me thought, "Shit, this could kill Etherpad". Then I tried Google Wave and realized that Etherpad was completely safe. I guessed wrong, Google still killed it.
I think the benefits of having a successful peer far outweigh your ability to use a free online text editor. Whatever loss in productivity is caused by the absence of Etherpad (or god forbid, having to use a G-branded version, or another service) can be made up for with the rush and motivation you should get from seeing one of your own get off the Ramen diet at last (or at least not have to worry if their effort will ever pay off; stuff like Etherpad will get built into browsers and OSes RSN)
Any big fish could have taken their client base without paying a dime; everyone from Skype to Computer Associates could have obsoleted them without even trying. Heck, Open Source IM packages like Pidgin could easily add a service like Etherpad and those boys would have labored for nothing.
If you don't like what I am saying, the next time you cash out, just know that I am just as happy for you :-)
Saying that everyone could have obsoleted EtherPad is like saying Intuit could have obsoleted Mint - Hard to argue with except by pointing out the facts on the ground don't support that version of reality.
Etherpad ROCKED - I've spent a couple weeks now with Wave, used it for a bunch of projects, and every time I use it, I did so grudgingly, realizing that Etherpad was lighter, cleaner, and more elegant compared to Wave's all-in-one platform approach. Yes, it's true that I can insert YouTube Videos, Polling Systems, and even a freaking ChatServer into my WaveDocuments - but it always felt like more of a technology exercise than a useful use of an application.
Let's hope that the EtherPads can do for Wave, what the Mint Team will (hopefully) do for Intuit.
That's like saying it's good when a band starts making music to make money instead of to make entertainment/for the love of music. It's great for them that they have profited from their effort (and they have the right to do so) but the ultimate goal of all this should be to make the world a better place in some way, not to make money. Creating a sustainable way to improve people's lives is the goal.
The band comparison is a fallacy: musicians are not in my line of work, I don't watch musicians for social cues and I sure as hell do not use their business decisions, lifestyle and success as a benchmark for my own. Software developers and entrepreneurs I do.
Game recognizes game, and right now I don't see much of it in this thread.
I used JotSpot, not too heavily, just as a company intranet. Google Sites definitely streamlined everything. Maybe because I'm not a power-user or whatnot. But Google Sites is way easier, leaner, and faster for me at the end of the day.
Don't conflate Wave-the-framework with Wave-the-product. A lot of time and effort were spent on Wave-the-framework, whereas Wave-the-product feels like a first cut demo. I assume that Wave-the-product will go through a number of revisions that will be more Docs like, and I expect EtherPad to be a part of that.
Also, Wave-the-product might just be one client Google releases. If they really want to encourage a "Wave ecosystem," they'll likely pump out multiple clients with different focuses (including, hopefully, a new Wave-the-framework-backed Etherpad.)
Again, product versus framework. XMPP as a communications framework has decent adoption, a number of open source servers and clients libraries in different languages. Jabber has limited adoption because its competing in a network-effect field. GoogleTalk is probably the most popular use of XMPP.
But, the meat of Wave isn't XMPP, its the combination of Operational Transforms on a federated XMPP layer with a web interface. Each of these features is equally important, so don't overlook them. OT makes collaboration easy, the web interface is the easiest user experience, and XMPP lets you scale the backend.
Congratulations to the AppJet/Etherpad team. When I thought about your "exit" options, Google was at the top of the list. This doesn't surprise me given how talented you folks are and the real-time web expertise that Google needs more of these days.
It really really sucks to see Google shutting down Etherpad though. We used it at Poll Everywhere quite a bit for collaborative coding, now we'll have to find something else. Any chance you could convince Google to keep Etherpad around in some form?
Runs on OS X is a bit of an exaggeration though. It can supposedly be installed through MacPorts, but the two times I ever tried, MacPorts installed about half of normal Linux distro, before failing on some broken dependency.
If you want to go through several hours of compiling and several hundred megabytes of dependencies, with your fingers crossed that things won’t inexplicably break 3 hours in, feel free to try to install Gobby on a Mac. Personally, I’ll stick to SubEthaEdit, or whatever web-based editor, if I need collaboration.
* * *
I really think desktop collaborative editors should try to provide a web-based alternative front-end, for just this reason, that it’s nice for everyone to be able to contribute, and there’s no better way to ensure that than through the web.
I was a heavy appjet user. It was indeed an awesome system.
I think there were two reasons it didn't succeed:
1. It's niche was razor-thin. It required some skill to use, but was so minimalistic that many programmers would prefer to take the extra time to set up a "real" server.
2. Too ahead of its time
I suspect tools like appjet will be commonplace in a couple of years. In fact, I wouldn't be surprised if the "Google Wave" thing is a ruse and that these guys are actually working on an online editor for Google App Engine... This could, in theory, turn Chrome OS into an awesome dev environment, no?
I used AppJet myself for small personal projects, and liked it a lot. However, it wasn't complete enough for commercial use, perhaps as a platform for another startup to build their web app on. For example they didn't support development outside their web IDE, multiple code files in a project, a storage system with known scalability properties, or paid accounts with higher resource constraints.
I know they were working on at least two of the four features I mentioned above before they decided to abandon AppJet in favor of EtherPad. Building their own app to prove their platform was a good idea, but I guess they just didn't have enough resources to work on the app and the platform at the same time.
I'm not sure what the AppJet guys would have considered success to be, but if they expected other companies to build commercial apps on top of their stuff I think they gave up too early.
"Does anyone have any theories on why appjet never took off as a product?"
Basically people aren't going to switch to a new way of doing text unless someone forces them. Only a very small minority of people use something like FreeMind or EverNote instead of Word as their primary writing tool, so how could appjet ever hope to get more than a tiny fraction of those people when their best functionality only works when you have multiple people?
The only way to get mass adoption would be to force people to use it, which is possible, but only if you design the company around that from the ground up. Which I don't think they were organized to do, at least as far as I can tell.
If Google wants to, they actually have the ability to force more people to use it. Not sure if that will happen, but I hope it does since I wish I were able to use it more myself.
this feels silly, but is this opening an area for a new startup to clone them? They'd only be down one exit option. Albeit a very big nice exit option, but there are obviously people that would use their product.
The obvious way to make it more valuable is to integrate a web version with other editors--be they rich text or not. I'm not sure how easy it is to plug into Word, but seems like that could add lots of value.
Congratulations to the Etherpad team. It's too bad that AppJet never took off more as a product; It seemed like it had a lot of potential. Etherpad was a lot of fun- I used it internally on a few projects, after seeing PG's demo with playback.
Hopefully you can add that feature to Google Wave while you're there; It was by far my favorite aspect of Etherpad. Even thought I can copy and paste my Etherpads into G:Wave, I can't keep the history, so that'll be gone forever in March, it seems.
There's no better tool for text collaboration right now.
I've been using it for my interview transcripts. With Etherpad, I can let 12 people on Mechanical Turk each transcribe a 5-minute section of my interview. And they can all be on at once and none of them needs and account.
I don't understand all the negativity about etherpad being killed in this thread. Sounds like an opportunity to me...if you reckon it's so useful, and google are going to kill it, then go build etherpadv2 and charge for it. :)
I actually did a ton of research on this a few weeks ago to figure out which collaborative editor to embed in my blog, and I'm sorry to say, EtherPad is 100x better than the nearest competitor, which is probably Google Wave or Google Docs.
Frankly, the best alternative is to try to scrounge around for old EtherPad URLs and just reuse them until March. :(
Squad is one of my passion projects. And while I love it, I've never really thought of it as a competitor/replacement for EtherPad.
Squad serves a great purpose for developers working together on code, but it isn't embedable, and doesn't do wysiwyg text formating. It's focused on syntax highlighting and opening and saving local files. So for some it may be an alternative, but not for everybody.
This seems to me like a classic case of a company buying another company just for it's patents. I'd be willing to bet that the main reason Google is buying Etherpad is their synchronization patent and any other patents Etherpad owns that cover the functionality of Google Wave. Google probably won't use any of the Etherpad code in Wave.
TechCrunch is claiming 8 figures, which would be a bit high for a simple talent acquisition. Seems like a talent+tech acquisition, more along the lines of FriendFeed than Parakey or Pownce.
Edit: Parent formerly read: "...Seems like PR spin. Instead of shutting down a startup and going to work for big.co and risk being called out as a failure, work out a deal with big.co to 'aquire' the startup then shut it down. Maybe we need a new word for a talent acquisition, where the startup is shut down and just acquired as a more optimized way of hiring. ..."
I am somewhat interested in their comet container which is based on JVM + Rhino. I am guessing they've rolled their own (using their raw NIO or Netty), rather than go with Jetty's "Continuations". I wonder if there's any chance Google will open source it, much like Facebook outsourced FriendFeed's Tornado?
I am also curious about their distribution model (how do you provider a consistent experience if this is to run on multiple machines?) -- or lack thereof (do they use load balancer "magic" to ensure that all collaborating on a single specific session go to a single machine, potentially creating hot spots)?
We've been working on a solution with Operational Transform as well... but looking at the kind of demand you guys have for it, sounds like we (and other startups) should rush to fill the void left by Etherpad.
It seems like most of these guys came from Google in the first place, must be an interesting experience to leave a company, found a new company, and then have that company bought back. (I know it happens quite a bit)
If they tell us the $ figures, I am sure you will be motivated enough to discover the algorithms all on your own in an instant, or at least I would :-) High rewards have a tendency to induce epiphanies.
[Edit: Here is how I think it works, from my brief 2-day usage of it.
Comet: persistent connection between client and server.
First client connects to the server and creats a session. Server creates a "channel" with a file-handle/chan-id. Subsequent clients follow a URL to join the channel.
Without the live editing, you can see how any write in one client's textarea can be sent to the server and broadcast to all the channel members.
To allow for live editing, server keeps a "buffer" for the channel, initially empty.
At the start, the server sends a test packet to each client and sees how long it takes, for timing purposes, call the time it takes to get a PONG response L for lag. So in the future, when a client sends a text snippet, it's timestamped, and the server subtracts the lag to get the actual sending time.
Along with timestamps, each text segment is also ID'ed by user, this allows the rendering engine to assign colors to the text.
Just wild speculation after giving this no more than 5 minutes of thought and another 10 to type it.