Re: [backstage] Google Wave - Too early for consumers
As the banner graphic on Wave points out: its a "preview" - in my understanding that means it is not even something they'd consider calling a beta. My gut feeling is that performance issues are as likely to be down to the client implementation as the servers - I think I'm noticing gradually worse slowdown the longer I use a session in a tab. Also look at your CPU usage when, for example, you use the history "playback" function, or open a particularly complex or long lived Wave. Matt On Wed, 02 Dec 2009 13:15:59 -, Ian Forrester wrote: Hi All, I was at Social Media Café Manchester yesterday and there was a session about Wave. I and Paul Robertson stated the fact that the "wave" people are there seeing isn't wave at all. Its simply a rough cut implementation of what's possible with the wave protocol. http://search.twitter.com/search?q=&ands=wave&phrase=&ors=¬s=&tag=smc_mcr&lang=all&from=&to=&ref=&near=&within=15&units=mi&since=2009-11-30&until=2009-12-02&rpp=15 So during the rest of the discussion and reading this - http://orchard.co.uk/Blog/Google-Wave-much-maligned-but-missunderstood-128.aspx, I'm wondered if Google had put out wave too early for consumers? What do others think? Secret[] Private[] Public[x] Ian Forrester Senior Backstage Producer BBC R&D North Lab, 1st Floor Office, OB Base, New Broadcasting House, Oxford Road, Manchester, M60 1SJ - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/ -- | Matt Hammond | Research Engineer, FM&T, BBC, Kingswood Warren, Tadworth, Surrey, UK | http://www.bbc.co.uk/rd/ - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] Google Wave - Too early for consumers
2009/12/2 Stephen Jolly : > > > I'm also not convinced [of] the performance issues with the Wave beta I expect this to work like multiplayer deathmatch game server services. -- Regards, Dave - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] Google Wave - Too early for consumers
On 2 Dec 2009, at 13:15, Ian Forrester wrote: > So during the rest of the discussion and reading this - > http://orchard.co.uk/Blog/Google-Wave-much-maligned-but-missunderstood-128.aspx, > I'm wondered if Google had putout wave too early for consumers? I can't say I agree with Andy Chesters - Google announced the open source, open standard nature of Wave right back when the project itself was made public at Google I/O 2009: http://googleblog.blogspot.com/2009/05/went-walkabout-brought-back-google-wave.html No desire to "to hide the fact that the technology is not exclusive to Google" that I can see. I'm also not convinced that the performance issues with the Wave beta are mainly (or even slightly) due to the fact that all the current Wave servers are running in Google's data centres. Surely the spread of Wave servers to the far corners of the Internet will make things worse, as bandwidths fall and latency rises between the servers participating in a given Wave? Waves with participants who all use the same server might see a performance increase I guess, all other things being equal. S - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] Google Wave - Too early for consumers
2009/12/2 Ian Forrester : > > > seeing isn't wave at all. Its simply a rough cut > implementation of what's possible with the wave protocol. Right; the protocol seems sound enough, and I expect that (like Novell) it will get picked up by projects that would have had to have done the engineering on such a protocol themselves. But there are relatively few of those projects, and so I don't expect it will be soon that we see anything 'wow'-worth out of Wave. I think it will get subsumed by projects that use it and we will know those by their own names and indeed may come to know Wave itself by those names; like people who use the web and that the web _is_ the internet... > wondered if Google had put out wave too early for consumers? As Scot said, its hardly had a consumer release. Anyone who is involved in projects that might make use of such technology have heard about it, understand it, and probably by now have a beta account. What's the fuss? :-) - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
Re: [backstage] Google Wave - Too early for consumers
On Wed, Dec 2, 2009 at 13:15, Ian Forrester wrote: > > So during the rest of the discussion and reading this - > http://orchard.co.uk/Blog/Google-Wave-much-maligned-but-missunderstood-128.aspx, > I'm wondered if Google had put out wave too early for consumers? > > >From the post "Had Google have waited maybe a year or two longer, and launched a slicker product," I think Wave would never have been a slick product at release, no matter how long they kept it either closed completely or in developer only preview. Had they waited longer it might have been a bit quicker and a bit less buggy, but it would still have left a lot of people confused. In order to be a great product, it's going to need a lot of people giving it it a try and telling Google what works and what doesn't. Which means releasing a half baked product to relatively few people and telling them from the start that it's half baked and that their comments and criticisms are needed - which is what the Wave team have done. Thinking about it, I would challenge that it has been put out to "consumers". When Wave is open to everyone without an invite, then it will have been released to consumers. At the moment, most of the people using are more early adopter than average consumer. Scot
[backstage] Google Wave - Too early for consumers
Hi All, I was at Social Media Café Manchester yesterday and there was a session about Wave. I and Paul Robertson stated the fact that the "wave" people are there seeing isn't wave at all. Its simply a rough cut implementation of what's possible with the wave protocol. http://search.twitter.com/search?q=&ands=wave&phrase=&ors=¬s=&tag=smc_mcr&lang=all&from=&to=&ref=&near=&within=15&units=mi&since=2009-11-30&until=2009-12-02&rpp=15 So during the rest of the discussion and reading this - http://orchard.co.uk/Blog/Google-Wave-much-maligned-but-missunderstood-128.aspx, I'm wondered if Google had put out wave too early for consumers? What do others think? Secret[] Private[] Public[x] Ian Forrester Senior Backstage Producer BBC R&D North Lab, 1st Floor Office, OB Base, New Broadcasting House, Oxford Road, Manchester, M60 1SJ - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
