Re:Apache Wave
by otoburb on Friday April 04, 2014 @12:54PM
(#7532689)
This is specific, believable and (most importantly) falsifiable advice. Hopefully Apache Wave developers will consider this seriously and, after implementing email & chat integration, review post-implementation adoption rates
[ Parent
| on HN ]
There has been some work on integrating Wave with email (initially as a way of using Wave as some mailing-list replacement tool). See WAVE-70 (https://issues.apache.org/jira/browse/WAVE-70).
Chat integration is arguably simpler - and Wave already understands XMPP (for federation), so it would be possibly to map Jabber -> Wave (say). How you would want to map from Wave -> Jabber is more complicated (as any blip at any point in the tree, can be edited at any time, by anybody)...
Here's what the email-wave integration looks like:
Editing existing conversations: http://imgur.com/a/GtGY6 Inline replying: http://imgur.com/a/Dkefp
Re:Apache Wave
by StefanKarpinski on Friday April 04, 2014 @12:57PM
(#7532713)
I'm pretty sure that the Wave project already spent all its credibility. When something is hyped that hard and fails that spectacularly, it doesn't tend to get a second chance.
Re:Apache Wave
by waterlesscloud on Friday April 04, 2014 @03:10PM
(#7533625)
AI and VR say otherwise. :-)
AI and VR will always be cool (at least until they're done right, then they'll be just as boring as an iphone); email replacement? not so much.
99% of people don't even remember Wave anymore, so I'd say they kind of have a blank slate.