←back to thread

358 points ofalkaed | 1 comments | | HN request time: 0.266s | source

Just curious and who knows, maybe someone will adopt it or develop something new based on its ideas.
Show context
BirAdam ◴[] No.45554716[source]
Google Wave.

Edit: you asked why. I first saw it at SELF where Chris DiBona showed it to me and a close friend. It was awesome. Real time translation, integration of various types of messaging, tons of cool capabilities, and it was fully open source. What made it out of Google was a stripped down version of what I was shown, the market rejected it, and it was a sad day. Now, I am left with JIRA, Slack, and email. It sucks.

replies(13): >>45554837 #>>45554843 #>>45554892 #>>45554995 #>>45555111 #>>45556098 #>>45556279 #>>45556288 #>>45556513 #>>45556725 #>>45559672 #>>45560207 #>>45564011 #
socalgal2 ◴[] No.45554892[source]
I was blown away by the demo but then after I thought about it, it seemed like a nightmare to me. All the problems of slack of having to manually check channels for updates except X 100 (yea, I get that slack wasn't available then. My point is I saw that it seemed impossible to keep up with nested constantly updated hierarchical threads. Keeping up with channels on slack is bad enough so imagine if Wave had succeeded. It'd be even worse.
replies(3): >>45555700 #>>45556303 #>>45565775 #
1. pwlm ◴[] No.45565775[source]
Twitter has hierarchical threads and it succeeded.

Mailing lists use hierarchical threads and they haven't gone away.