Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread David Bolen
Aahz writes: > It sounds like Wave requires a high-powered browser, similar to Google > Maps. That makes me -1 because I want to continue using Lynx. I'm not sure - I think you can implement your own choices at different points. What's interesting to me so far is less the current UI/flashiness

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread Jake McGuire
Google Wave is also still in tightly restricted beta. Gmail went through a long invite-only period. Until we have an idea of how long it will be until basically all python developers who want a Wave account can get one, it doesn't make sense to talk about using it for python development, IMO. -j

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread A.M. Kuchling
On Thu, Jun 04, 2009 at 01:15:16PM -0400, Terry Reedy wrote: > marked as having new content. At your leisure, you open it (or perhaps > you have marked it 'download updates in background'). That that takes > longer with a slow connection is no different than with other text > streams. If y

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread Terry Reedy
Ben Finney wrote: Terry Reedy writes: Ben Finney wrote: I watched [the Google Wave presentation] too. It appears to be heavily reliant on *very* fast internet access for participants in a wave. That's far from universal in the Python community, let alone the internet at large. Even a slow co

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread Aahz
On Thu, Jun 04, 2009, Terry Reedy wrote: > > Example: if PEPs were waves, then responses could either be entered as > live edits (with permission) or comments immediately following the > relevant text (as with email/newsgroups) visible to all. Much easier > than current situation. Edits are

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread Ben Finney
Ben Finney writes: > Terry Reedy writes: > > Even a slow connection would make participation in PEPs better than > > today. > > How can you know that? A slow link doesn't punish email or NNTP > communication the way an interactive web application does. Strike that; reverse it. Should be “A slo

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-04 Thread Ben Finney
Terry Reedy writes: > Ben Finney wrote: > > I watched [the Google Wave presentation] too. It appears to be > > heavily reliant on *very* fast internet access for participants in a > > wave. That's far from universal in the Python community, let alone > > the internet at large. > > Even a slow co

Re: [Python-Dev] Google Wave as a developer communication tool

2009-06-03 Thread Terry Reedy
Ben Finney wrote: Terry Reedy writes: I watched and was greatly impressed by the video demo of Google's new Wave collaborative communication system. I believe it would/will help with some of the chronic problems we (and others) have. Example: if PEPs were waves, then responses could either b

Re: [Python-Dev] Google Wave as a developer communication tool (was: Issues with process and discussions (Re: Issues with Py3.1's new ipaddr))

2009-06-03 Thread Bill Janssen
Ben Finney wrote: > Terry Reedy writes: > > > I watched and was greatly impressed by the video demo of Google's new > > Wave collaborative communication system. I believe it would/will help > > with some of the chronic problems we (and others) have. > > I watched that too. It appears to be hea

[Python-Dev] Google Wave as a developer communication tool (was: Issues with process and discussions (Re: Issues with Py3.1's new ipaddr))

2009-06-03 Thread Ben Finney
Terry Reedy writes: > I watched and was greatly impressed by the video demo of Google's new > Wave collaborative communication system. I believe it would/will help > with some of the chronic problems we (and others) have. I watched that too. It appears to be heavily reliant on *very* fast intern