Google Wave Looking To Join Apache Software Foundation 79
MMacFadden writes "The Google Wave team has officially submitted the open source version of Wave to the Apache Software Foundation as a candidate Incubator project. Google hopes that the wave technology will continue to grow, supported by the new open source community (which is made up of Google and non-Google employees alike). Here is the proposal itself."
Hope (Score:5, Interesting)
Re:Hope (Score:5, Insightful)
great app, lousy implementation (Score:3, Interesting)
I think a second problem with Wave was that the implementation sucked. They built Wave using some kind of Java toolkit that hid the JavaScript frontend code from programmers. As a result, the page the user interacted with was slow and inflexible. There was more Java library and framework bloat on the server. Writing extensions for it also was unnecessarily cumbersome. For example, the content of a wavelet wasn't in XHTML subset as you might expect, it was in some weird attributed text format. Just get
Re: (Score:3, Insightful)
For me it depended on the browser. With Firefox it was slow, okay with Safari, and seamless with Chrome. Not surprising, and probably wouldn't still be the case had they not abandoned the project. Although it's a niche product, it's really good at what it does and has the potential to be great. Hopefully the open source community does some neat things with it.
Re: (Score:1)
It's not just the fact that it was slow; the user interface had problems, it didn't work on mobile devices, and the APIs were bad in places as well.
I'm not sure WIAB a good thing to build on; PyGoWave may be a better platform to build on.
Re:great app, lousy implementation (Score:4, Insightful)
Re: (Score:2, Informative)
Re: (Score:2)
Re: (Score:1)
Fair points. Wave may indeed be successfully used in collaboration products like Pulse, and that would be good. But for me that would still be a very disappointing outcome and is what I had in mind when I wrote 'languishing in obscurity'. The great promise and potential, which sadly won't be fulfilled, was for collaboration and communication across broader communities beyond one company or group of friends.
There's nothing stopping someone from setting up a service similar to Google Wave using the open source implementation. Let us get version 1.0 out the door and we'll see what happens :)
Re: (Score:2, Interesting)
Making an Amazon EC2 image might help.
Re: (Score:3, Insightful)
They built Wave using some kind of Java toolkit that hid the JavaScript frontend code from programmers.
Let's call the demon by its name: Google Web Toolkit [google.com].
If they had hand-coded the frontend and written a lightweight backend, Wave would likely still be around.
I'm not so sure about that. Wave didn't fail for technical reasons. It failed because there was no transition path (No mail gateway for a mail replacement? wtf? XMPP-IM at least gets that part right.) and bad management (they expected a private beta for a walled garden solution to take off immediately).
Re: (Score:2)
Adding SMTP and other features isn't rocket science. The reason it took so long was probably because they were bogged down by their unwieldy software infrastructure.
Re: (Score:2)
Having written applications with GWT, I find it anything but unwieldy.
Bringing static checking, JUnit-based testing, and modern code coverage tools to JavaScript (and doing a ton of micro-optimizations during the compilation process under the hood) does a world of good. Letting Java-based debugging tools be seamlessly used for debugging JavaScript is even better.
I've seen attempts to implement a GWT-like toolchain for other languages (Python, Scheme) -- and the competition all falls down not on having effec
Re: (Score:2)
The "software infrastructure" I was referring to wasn't just GWT.
Furthermore, while GWT makes you happy as a Java programmer, it made me unhappy as a user, since there was no reason Wave had to be that slow and have so many browser incompatibilities.
Re: (Score:2)
GWT builds faster-executing JavaScript than I can write by hand in a reasonable amount of time, just as a C compiler builds faster assembly than most people can build without digging in and hand-optimizing. Likewise, it builds code optimized for different "targets" -- an IE6-optimized version, an IE7-optimized version, a Firefox-optimized version, etc etc. As such, it provides the tools to build a faster site with wider browser compatibility than one would necessarily be able to build without it.
Is this to
Re: (Score:2)
Why are you so hung up on GWT? I blamed GWT for the bad user interface, not the delays. Get over it.
Re: (Score:2)
You didn't make it clear exactly which issue you were blaming on which piece. The clarification is appreciated.
Re: (Score:1)
Re: (Score:2)
Well, what they accomplished was to have their project killed within 3 months of general release, so, yeah, I tend to agree.
Wave is Perfect for Real Estate (Score:3, Interesting)
Look at a Real Estate transaction: Clients, Realtors, Attorneys, and Bankers all collaborating on documents.
Right now we fax, mail, and email them around.
Imagine a wave-based real estate transaction where everyone makes tracked changes to a single document. It's perfect!
All that remains is the hardest part: the social engineering aspect. Because wave isn't useful if only one party is using it!
Re: (Score:1)
Re: (Score:1)
Re: (Score:3, Insightful)
I think the idea of Wave is still brilliant, but it does need some polishing. My biggest beef is with the user interface. A big wave can quickly turn into a confusing mess. What's new? What's old? What do I still need to respond to?
I need more tools to manage my view on the wave. Close bits, split different subthreads with diverging topics into separate waves, flag messages as read, unread, important, interesting to others, archive-worthy, etc.
The technology is very powerful, but it needs a better UI to do
Re: (Score:2, Interesting)
Player Corporations in Eve Online running a wave for each corp project worked out well.
Discussing a small FOSS projects with a group worked for those of us not logged into IRC 24x7. Setup your trac or build environment to post. Start feeding build reports into it and starting waves for project forks.
Sure, if you live on Facebook or in IRC and mailing lists wave is more of a 'why would I care?'
Needing to put effort in is the key problem with any pa
Re: (Score:2)
Me too, since with a little more glue code and maybe integration into some existing Free software it could be several parts of a really good learning management system.
Re: (Score:2)
Not a bad protocol per se (Score:1, Interesting)
I liked the idea of SOME of the things in wave. My hesitation came from the fact that I couldn't easily port it over to my email. If I could do everything in one place, I'd have been happy. You also had so much crap going on in a single wave that it was impossible to tell what the hell was happening. I felt like I needed a diff to figure out what was going on.
The wave protocol, if I remember, was pretty open and allowed distributed servers. I'd like to see that take off at some point.
Re: (Score:2, Informative)
Hosted Wave (Score:1)
Re: (Score:3, Informative)
Re: (Score:3, Informative)
Maybe I need to RTFA, but I just went to http://google.com/wave [google.com] and it worked fine. I know it's no longer developed, but it still exists
Re: (Score:1)
Maybe I need to RTFA, but I just went to http://google.com/wave [google.com] and it worked fine. I know it's no longer developed, but it still exists
Not for long. Earlier, Google announced that they would wrap things up with Wave, but they also said that the service would stay alive at least until the end of this year. (They probably just want to give people a headstart if they want to move their stuff away from Wave.) After that, it's anyone's guess.
Re:Hosted Wave (Score:4, Informative)
Part of the incubator project is WAIB (Wave in a Box) - which you can download now off the main Wave Protocol website (www.waveprotocol.org) which allows you to run your own Wave Server - including a supplied web interface. The Wave protocol includes federation so you can link up WAIB.
Good (Score:2)
Re:Good (Score:4, Informative)
Do you have a link to the youtube video?
Here you go:
http://tinyurl.com/yjuygc3 [tinyurl.com]
Re: (Score:2)
Re: (Score:2)
Please don't use URL shorteners here. They make it impossible to see what domain the URL actually points to, and there's no practical limit on how long of a link you can use in an <a href> tag on Slashdot.
I just hope that Google cleans up their act (Score:4, Interesting)
Here's why:
I have a Chrome bug to submit, log onto my Google account, type details of my bug and sadly, I find the 'submit' button disabled.
Sometimes, I am not surprised that Google Wave "bit the dust."
Re:I am just glad that epSos.de is helpful (Score:1, Informative)
Google is overwhelmed with bug reports.
Go to their support group forums for developers where the actual employees read.
Re:I just hope that Google cleans up their act (Score:4, Informative)
Re: (Score:1)
In this sense, developers are a lot like users-- they don't know how to interpret the gobbledygook that is a stack trace or memory dump unless they know to some degree of precision how the program got there, and if the problem is predictable and/or repeatable. Unless the dump matches a previous case perfectly, a null pointer (for example) can be due to any reference to memory.
Long story short, tell the devs as much as you can if you really want the bug fixed.
Re: (Score:2)
Yes, because all software undert he ASF envelope is 100% bug free and feature complete.
What kind of nonsense is this? What does a minor bug on a web-page have to do with submitting a project as open source?
It was the packaging that killed it (Score:2)
Selling wave as an email replacement was a mistake.
The packaging that wave came it was what killed it.
A group of people could work on a document, or stream of thoughts, refining things as they went... that part was brilliant.
The insistence that each person had to "own" a piece of it.. meant each document was a chain of links, instead of a seamless whole.
This packaging choice killed the usability, and lead to the downfall of wave.
Let's hope this can be overcome in the next iteration.
Re: (Score:2)
It works fine. Google is just not going to push it anymore. They hope other people are going to pick it up and turn it into something cool. Who knows, they might even jump on board again when it gets some impetus. Joining Apache is certainly a good step in that direction.
Re:WAVE still exists! (Score:5, Informative)
It's going to be shut off in about 2 months, and they reassigned the entire team to other projects and the creator left to go to facebook, who just days ago announced an effort on a project "to replace email" with something more collaborative and real time.
Where have you been?
Re: (Score:1, Troll)
who just days ago announced an effort on a project "to replace email" with something more collaborative and real time.
What? Reference, please.
Re:WAVE still exists! (Score:4, Informative)
http://gizmodo.com/5690405/facebook-email [gizmodo.com]
http://techcrunch.com/2010/10/29/rasmussen-facebook-google/ [techcrunch.com]
http://www.google.com/ [google.com]
Re: (Score:3, Informative)
http://googleblog.blogspot.com/2010/08/update-on-google-wave.html [blogspot.com]
Re: (Score:1)
It's there now, but I suspect will be going away in a few months. We can hope though!
They always get the WHY of it wrong. (Score:3, Interesting)
Wave was an amazing idea with some really poor implementation. Having wiki capabilities but no revision control? Duh. No way to create some sort of social grouping or mailing list or whatever. Not letting the wave creator kick people from the wave. Not letting the wave creator set even basic editing privileges. Wave didn't fail to take off because it was confusing. It failed to take off because it wasn't even ready for alpha status. They should of spent less time trying to shove it as some sort of email replacement and more time making it at least work.
Re: (Score:1)
Wave had revision control. You could roll back. It might not have been a perfect implementation but it was there.
You could create groups, add them to waves, and have them notified through email. It again wasn't that friendly/easy, but it was there.
You could kick people from a wave. It wasn't there in the early versions but was implemented and working in later revisions.
You could allow people read and/or read/write capabilities. This too wasn't there in the early versions but was implemented in later revisi
Re: (Score:1)
...
Let me help you out with your why wave failed ...
It had nothing to do with how well it worked.
Wave 'failed' because no one found any usefulness to it. It tried to fill a roll that no one needed filled.
Re: (Score:1)
That wasn't our experience at all. We used the hell out of it, and still do. We'll also be running WiaB. We don't have anything to replace it, and we don't want to go backwards. It absolutely filled a hole that we were needing filled.
Re: (Score:2)
If you think nobody has any use for group collaboration software you are nuts.
Re: (Score:1)
I agree, Wave is an amazing idea.
Love it, and would want to work more with it, hope the change makes it easier for people to start picking it apart and doing more cool things with it.
What's not to love? It's an instant protocol over the web. Wonderful.
Re: (Score:1)
From the blog
In addition, we will work on tools so that users can easily “liberate” their content from Wave.
Re: (Score:2)
You can export your waves [blogspot.com] right now.
Big Damn Protocol (Score:2)
What did they expect after making those references?
Now please go and do the impossible. :P