Slashdot Mirror
Google Kills Wave Development
We've mentioned several times over the past two years Wave, Google's ambitiously multi-channel, perhaps plain overwhelming entry in the social media wars. Now, reader mordejai writes "Google stated in its official blog that they will not continue developing Wave as a standalone product. It's sad, because it had a lot of potential to improve communications, but Google never promoted it well, denying it a chance to replace email and other collaboration tools for many uses."
First wave (oh no, they killed it)
To Wave Goodbye.
Get it?
It kind of goes to show how full of shit most tech blogs are. Almost all of them were talking about how Wave was the future, absolutely, after watching one indie youtube video about it explained in cute crayon drawings.
Perhaps there should be a rule for them. Just as with companies using the products they make is called eating their own dog food, blogs who promote someone else's failed product should have to eat their own dog shit.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
I really enjoyed watching Chrome swell up to 3GB resident memory, and then detonate, while wading through all that dynamic "content." The core files were... remarkable.
Lurking at the bottom of the gravity well, getting old
Morpheus: Unfortunately, no one can be told what Google wave is. You have to see an indie youtube video for yourself.
Please don't like Gmail or Google Calendar. I don't won't those to go away too! ;)
Wait. Do you claim Sharepoint is dead like Wave?
Use a development model that isn't just a bunch of bullshit buzzwords for a middle-out model? Perhaps use amazing modern technology like the telephone or email, and actually put someone in charge of your project instead of relying on flaky feelgood collaboration? Maybe use a repository like the rest of the software world? Or simply join a rugby club where your agile scrum and collaborative sprint abilities will be rewarded?
Glad to help.
*waves*
Please read my Canon EOS tech blog at http://www.everyothershot.com
Maybe the problem was that the users of Wave also used phrases like "hyper rapid content development among small groups of dispersed people." Painful.
Painful.
It's buzzword friendly! It allows you to leverage your synergies or something.
hyper rapid
lol, try saying "very fast" and then maybe normal people will take you seriously :)
I dont read
Don't rely on a single product to guide your team. That's why you have a team leader. They are in charge of making sure you have the most effective tools at your disposal so your team can work efficiently. Multiple products that they know work well enough together that your team can benefit from using them in conjunction with one another. Sometimes one component of the system won't work well with others. The team leader replaces it; and life goes on.
Use Google Docs or something similar to easily share documents and resources.
Use Git or SVN to have a repository for your project if multiple members write code that's updated regularly.
Use the phone to call someone when it's urgent or text them if you can wait for a response. Still feel free to email people as an alternative method of communication. Use Skype, or just about any other instant messenger. Don't rely on just one thing.
Rely on your team leader, that's why you have one. Can't reach someone or somebody isn't putting in their fair share of work? The team leader ultimately takes care of that, whether by removing the offending member or reprimanding them.
Specifically, our team uses Git to access a repo hosted on ProjectLocker. PivotalTracker helps keep our features, deadlines, and bugs prioritized; and we're looking into using Trac for bugs and issues. We use Google Docs to share resources. We email each other constantly; have each other's phone #s; and sync up via Skype at least once a day. There are a few hiccups here and there, but you learn to roll with it and keep on going.
Life. Is. Good.
I guess the guys at Google couldn't figure out what it was for either.
You mean, things like "redefine turn-key web-readiness," "iterate cross-media platforms," or "unleash proactive schemas"?
"The body may heal, but the mind is not always so resilient." -- Deus Ex: Human Revolution
Standardisation is never "hyper-rapid".
I am going to hunt down and kill the next person who uses "hyper-rapid" in this thread :)
I dont read