News for hackers. Stuff that matters.
Re:How not to replace email: lessons from Google Wave by jasonlotito on Sunday February 18, 2018 @10:02AM (#16406343)
Wave didn't have a UI, it had clients. Google's client might have been a problem, but that would be like me complaining about email because the client I'm using one accepts a single email address at a time.
Re:How not to replace email: lessons from Google Wave by opencl on Sunday February 18, 2018 @11:36AM (#16406789)
If every email client currently in existence only accepted a single email address at a time it would be a perfectly valid complaint about email. It's like all those W3C standards that none of the browsers actually implement, "it's not a problem with <protocol> it's just a problem with every implementation in existence" is not a useful distinction to make.
Re:How not to replace email: lessons from Google Wave by tatersolid on Monday February 19, 2018 @10:54PM (#16417730)
> If every email client currently in existence only accepted a single email address at a time it would be a perfectly valid complaint about email.

Sounds like Nirvana to me. No more eternal “reply to all” chains that span months? I’m in.