A lot of snarky sniping goes on online, most of which is easily dismissible. Sometimes you have to appreciate some of the snark for its simplicity.

According to 'easiertounderstandthanwave.com', A swedisch chef is easyer to understand than Wave (73%), even our own Existance (61%), Death, Cardiological Surgery (55%) or neoclassical Economy (60%) are easyer to understand than Wave - but, at least Wave is easyer to understand than Sarah Palin (74%), Microsoft Visio (74%) or Obama's nobel price (67%)! (refresh the site to see more comparisons)

So, it looks like shrikant (trialrun) is either a genius, understanding things like a swedish chef, Cardiological Surgery, Death, or even our own existance in less than a minute ... or he understood Google Wave so easily, because of his Colayer background ...

A lot of Google Wave logins have gone out these days, and a lot of people had the possibility to play around with it (if you havent yet gotten an account, pls let us know, we may be able to arrange a test account for you) -
What are your impressions? - What is great, what good, and what not so great in Wave? and how is it compared with Colayer? -
Is anyone interested in writing a comparison between the two products?

A blog post to the topic 'Wave and Colayer' could make a lot of sense right now: a lot of wave logins go out these days (also to journalists), a lot of people try it out, and would be interested also in exploring, what else is out there ...
Anyone interested? - and any way we could help / support you with this? - and yes, of course we will promote content, which is neutral or positive about Colayer ...

Useful overview to check 3.0 against!

sdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdf
ssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssd fsfdsdfssdfsfdsdfssdfsf dsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfds dfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfssdfsfdsdfss dfsfdsdfssd

... simply write your question into the virtual reception there - we will assist you then with colayer! - ... anyway, feel free to try around as long as you wish -

>The basic interface looks a lot like Gmail. This is generally good since Gmail is widely used and understood by millions of people.
>It looks like Google is trying to implement chat features with email. We can reply to someone's message like colayer context. One thing i
didn't liked was We cannot edit our notes by simply clicking on it. [rather than clicking on some menu/button].
>They have an inbox, which stores all the waves created, it might become difficult after some time to find out a particular wave if we have large no of waves.
>Its hard to findout which are the latest updates happened in my account.

To me, the Wave is a well-designed Comty. The Shuttle is not elaborate (yet?) but quite utilitarian, spartan even...

Notable bugs:

I can reply to an existing comment in a thread, only if there are other messages in a thread. Either that or the first level of replies is NOT indented.

The bloody wave is way too bulky. And I hate the bloody Spelly widget. It's typos & not spelling mistakes.

The possibility of adding widgets within a reply is interesting. It's as if I have an open HTML input box that's also WYSIWYG in the Google-sense - like a rich-HTML editor.

Seems slow to me, but that may be because it's trying to use a javascript to show you what I type as I type. POINTLESS, especially if there's no one on the wave with me.

And why do you BLOODY want to know what I type, WHEN I type it?? I am gonna submit my final response, aren't I? I like my edits private, thank you very much.

The interface is very email - so not much learning required. In usability terms, the wave has a sharper learning curve as compared to the Comties on the layer. Bitter truth.

There's a lot of help material available - text, videos, forums/fora, etc. But that may very well be because of a huge user-base.

It took me a week to understand how to use the Layer. It took me a minute to understand the Wave. That's how much difference usable interfaces make. Having said that, also admit that Colayer has far more potential as an enterprise collaboration tool, if the right niche is targeted. But the user interface, and the concept explanation need radical redesign. Bitter truth, again.

BTW, that's exactly why I will NOT take sides on any Wave v/s Layer commenting 'wars'... I still don't think that Comties are READY for a public ALPHA, let-alone the BETA...

Where do I see Wave in 12 months?

- Either adapted by all
- Rejected by all

Here's the gist:

If you create a new technology, you have to train people to use it. If you ride on an existing technology, people will learn to use it themselves. Standing out is not always an act of defiance - it could also be construed as an act of stupidity...

Pl note: Posting the EXACT same comment on the WAVE.

THANKS Shrikant for this opinion - yes, agree to most of it, and looking forward to great discussions about Colayer DAVOS towards end of year ... Why dont you make a blog post out of this? -
"It took me a week to understand how to use the Layer. It took me a minute to understand the Wave. That's how much difference usable interfaces make. Having said that, also admit that Colayer has far more potential as an enterprise collaboration tool ..."
Lets be realistic: that's where our great opportunity lies:
>> 'Colayer: Wave for enterprises ... and more!'
"If you create a new technology, you have to train people to use it. If you ride on an existing technology, people will learn to use it themselves. ..."
And what, if Colayer Davos integrates wave ONE-TO-ONE? What, if we make that the starting point of Colayer for enterprises? the EXACT wave interface?
>> 'Wave for enterprises ... and more!'
"Where do I see Wave in 12 months?
1) Either adapted by all
- Rejected by all"
Well, there are many ways in between, and probably it will be between - personally I think it takes longer than anticipated, but wave can be successful ...
But what would be the best strategy for Colayer in Both cases? -
1) We have to come as close as possible to Wave - Google intends to do a partnering strategy, and in that case, we may be able to get a high-end partner for enterprises
2) That would be not good for Colayer too - but: a lot of people will nevertheless spend a lot of time on Wave, and get educated ... and understand Colayer easyer ...

Fascinating how Google is reaching out to local companies to let them install Wave locally to then connect with others. This seems to be just out.

... it was always the intention of Google (announced already in the initial videos end of may): to make Wave & its components mostly open standards, for other software companies either to implement an own wave server, or to build an interface -
For Colayer, this is good news, as we have several options open for integrating or rebuilding Wave into the platform - Colayer would then be: "Google Wave for Enterprises ... and more -"
We monitor closely the development of Google Wave & the Federation protocol, but did not yet start implementing, for several reasons:
1) We currently focus all our resources on our new Platform Colayer 3 Davos -
2) Colayer 3 is currently not yet far enough for complex technology integrations
3) We think even Google Wave is not yet ready for Technology integration, as it is not even released yet - hence, we wait, until at least Version 1.0
4) We will have to make up our strategy according to Google's market strategy & success: If Google tries to build up technology partners, with own Wave implementation, we may try to go close to Google and become an 'official' partner - "Google Wave for Enterprises ... and more"
5) According to recent discussions, however, there are also quite a bit of concerns, that Google Wave may "take years to be mature enough to use for enterprises", or be "too complex" to use, or even "not be successful" (Anil Dash: http://bit.ly/1PdVql ). We will have to wait and see, how much Google will be able to make its standards widely usable, or if the full picture changes ...

What I found , when i first time use Google wave is this is nothing but my Inbox intead of email it shows me wave -
>it still have spam
>searching of my message (called Wave) in a huge Inbox in which after few period of time I will definitely got lost somewhere..:(
Main problem is to find updated things, that is if some wave is get updated (some one comment on that) it is in still like email inbox.
The google's claim of Contextualize Communication for wave is not 100% true (I will say it is only 30-40% contextualized), a colayer user definitely experience this.

I would like to check google wave from a Tester's Perspective

A Google Wave invite may have been a hot eBay commodity, but what do you do with it once you get it?

They are quite well known in the Indian blogosphere - Praval has 1500 Twitter followers!