Google Wave To Live On As 'Wave In a Box'

snydeq writes "Google Wave will morph into an application bundle for real-time collaboration, according to a blog post by Google Wave engineer Alex North. 'We will expand upon the 200K lines of code we've already open sourced (detailed at waveprotocol.org) to flesh out the existing example Wave server and Web client into a more complete application or "Wave in a Box,"' North said, adding that the future of the recently flat-lined Google service will be 'defined by your contributions. We hope this project will help the Wave developer community continue to grow and evolve,' he said."

Comments

It's my wave in a box!

[beanball75]

To all the fellas out there with ladies to impress, it's easy to do just follow these steps:

1. Cut a hole in a box
2. Put your wave in that box
3. Make her open the box

Wave in a box?

[sznupi]

An interesting workaround of the claims that it failed - now at least it's both alive and dead until we look. And how knows what that constant peeking might turn out in the long run...

Economy behind wave?

[drolli]

I guess google stopped it because they could not figure out how to allocate the amount of server infractructure needed and still earn money while keeping the service free. I actually would think that wave would reduce googles advertisement income because it would grow on the cost of other services while it has much harder demands on the computation power assigned to it than e.g. google mail. Its ok if an email takes a minute, but in the wave concept an minute would be long. With mail its even if it takes 20 Minutes a a busy time of the year.

Re:Economy behind wave?

[drolli]

Please contrast: google chat: i dont think much data is transported google voice: a moderate amount of data has to be relayed (1 hour of talking may be less than 10MB) - and not much storage at google is required (at least thats what i hope) google wave: if user a in Australia, user b in Europe and User c in America use the same wave, and keep it open over weeks in the expectation that, as soon as they sit down the system will react instantaneously, it will impose strong requirements on the database. If 100 Million users keep 20 waves requiring several MBytes open (remember what google suggested you do with it), then you may run into problem when you try to finance that on a free basis (which they had to do to circumvent the chicken-egg problem).

The only reason wave should be used...

[Idiomatick]

Small OSS projects. It replaces irc, todo lists, websites, messenger systems....... If you've ever taken part in a small oss project you'll know the spread out mess I'm talking about.

Wave COULD fix that and have everything combined. Integrate a bunch of features that are needed... like something to do difs and small file/code uploads. I'm sure depending on the project you could think of more things. It could do the job very well without much effort on the coder's part.

Re:The only reason wave should be used...

[JimWise]

I think there are MANY uses for Google Wave, but that is part of its problem. They are all very small, niche uses, which makes it hard to give a succinct description of it to someone and tell them how it could be relevant and useful to them. Also, since Wave is for coordinating with others it doesn't help to just persuade one person to try checking it out. They have to see a use for it and convince all the others on their project to give it an honest try too.

With GMail, the brand new Google Phone, etc, I just had to see that it could possibly be useful for me and try it out on my own. If it works for me, then great, I can just go ahead and use it. I can tell friends how useful they are, and since they are fairly single purpose tools they are easy to describe and simple for others to figure out if they are likely to be useful for them or not. Google Wave is much more amorphous.

Most of my friends are fairly geeky (yes, I know, quite a shocker for a slashdotter.) Back in March we started planning a group trip to Washington D.C.. We only had three weeks to plan (a friend's cousin was getting married out there and he mentioned to the rest of us just weeks in advance about it and in passing asked if any of us would like to take some days off to join in and do some sight-seeing.) Since we had limited time and couldn't all get together easily to plan we put Wave to great use. We were able to share links to points of interest, the metro system, possible places to stay; we created a roughed out itinerary that we could modify and you could click on each entry and it would show the location on the map so we could see what locations were in the vicinity to try to reduce unnecessary traveling back and forth, we put up a couple of polls for voting on what were the most and least desired to see by the group as we had to weed down a bit on what all we could do on our five day trip, and at the end of the trip we were able to share our photos with eachother. Wave allowed us to comment during lunch breaks and after work as time allowed, so even though we were unable to meet up in person or even on-line at the same time we could have group discussions about what we would like to see and do. Our trip went VERY smoothly and with the pre-planning we were able to pack in a LOT more than we ever could have otherwise on a trip like that.

My older sister just started up a new on-line magazine. She wanted to coordinate with others to figure out what format the magazine should take, be able to share and group edit the articles and layouts, have discussions about all of the physical, legal, IT logistics of getting the magazine started with the others involved, and asked me if I knew of something that could help them do all of that. I suggested Google Wave, and although the bulk of the people involved were from an English/Arts background they jumped in and found Wave to be indispensable since they all have "other" jobs while they are getting this off the ground so they do not have matching schedules or locations.

Wave can definitely start to get too unwieldy for large groups or very long running projects, so I agree with the "small projects" part, but I would definitely remove the "OSS" part.

Yes, a pine box...

[loraksus]

Also known as a coffin.

Re:Google's Wave product was dead on arrival!

[Dr_Barnowl]

Communications technologies depend on network effects. Gmail succeeded, despite restricting the number of subscribers, because it already had a vast network of email users to interact with. Mobile phones worked because they interacted with the existing phone system.

Wave was restricted to communicating with Wave. Getting the people you wanted to use it to sign up, grok it, then use it, was too much of an obstacle.

It's something different than an email replacement

[YA_Python_dev]

One thing that most people didn't get about Wave is that its mayor strength is providing an environment where humans and computers can easily communicate and work together.

Don't think about Wave as a super-email or super-chat or super-wiki, although it's a bit of all this, think of an interface that can be populated with custom robots that give to you and your coworkers easy real-time collaborative access to backends specific for your the work you're doing.

Like a form in a web site, that's highly interactive and can be accessed collaboratively by many people at once.

It had huge potential, but unfortunately very few people "got it".