As far as "collaborative editing environment(s)" go, I would love to see more alternatives with such capabilities.
What I found is that it turned IM-like communication into a high-bandwidth medium comparable to what you get in a phone conversation. It managed that while also retaining nearly all of the advantages of an IM client.
Oh god, please don't, at least not for chat/irc/whatever-you-call-it. I've seen so many attempts to try to somehow add another layer of order on top of chronological order. All the threads and whatever features and it is always a "what the heck is that, where are my messages, why did they get rearranged" disaster.
Like threads in e-mail, Usenet, forums on WWW?
IMO those are perfect examples of a combined logic and chronology. I'll speak for myself, but I absolutely prefer threads in the mentioned examples. It makes the content better readable. For me, there's no question about that. Although that isn't any proof; it'd be best to have usability studies about it.
If you're referring to conversation view, then they're not as good as traditional threads since they don't handle keeping track of conversation between multiple people that may branch off into different topics.
It never tried to hide messages from you, the threads worked more like filters. Instead of finding the discussion you wanted you filtered out messages that weren't related to that discussion.
Here's a demo video of how HN and Reddit could be modified to solve that, i.e. how chronological order could be added to HN:
https://www.talkyard.io/-32/how-hacker-news-can-be-improved-...
This part: "1. Finding new comments". I've actually implemented this for real — click "Recent comments" in the upper right corner
Some apps also do it, the app I use (Sync) will tell me the number of new comment and highlight them when I revisit.
Not sure what “back in the day” is for you, but I remember e.g. comp.lang.lisp being terrible in the 90s. And we all made jokes about flamewars, because flamewars were reality.
Even the dumbest of them would remember what articles you read and let you pick up where you left when you came back the next day. That's a straightforward feature that is sorely lacking on most web based discussion sites (Twitter does it, but is lacking in threading).
But functionality wise they were pretty good.
A properly implemented mail and news reader will indicate new messages in a threaded view after retrieving them. For example, Thunderbird viewing a usenet group makes it very easy to see new messages in threads after clicking on the "Get Messages" button.
To me the Thunderbird approach actually seems a bit annoying. What if I return after lunch, click "Get messages", and then Thunderbird highlights new comments in orange. But I don't read all of them, instead I go for another errand. Later, I return ... and click "Get messages" again. But now the orange marks from after-lunch will be lost, right? And only the very most recently loaded messages will get marked?
As far as I know, the thread overview pane will still show the unread message in a bold font, but the indicator that you just retrieved the message would be lost for the messages that you retrieved right after lunch (though it would then show up for messages you retrieved after you returned from your errand).
In either case, it would still be obvious which messages you haven't read as of yet which is something that HN doesn't really show on subsequent viewings of a given comment thread.
Perhaps Thunderbird could be extended to show a different symbol associated with each message retrieval so that, in your example, you would have one symbol for messages retrieved after lunch and a second symbol for messages retrieved after you return from your errand.
Whereas here at HN, it's a lot harder for the software to know which messages one has read (because here messages are shown without the user indicating what s/he is reading).
Yes perhaps different symbols — actually I'd be happy with just Thunderbird's bold font :- )
This is the sort of thing I love about the web, and composability in general I suppose.
The people who designed the HN UI didn't think or care about that feature at all, but just by virtue of the fact that the user has powerful general-purpose tools at his disposal, and the HN UI is just as valid as content as the actual content is, the user can piece it together for himself.
This would not be possible if HN were a traditionally-designed desktop application instead of a web page.
The web returns us lots of the composability that was lost when "progressing" from CLI applications to GUI applications.
Here's one way to show new comments at HN: https://www.talkyard.io/-32/how-hacker-news-can-be-improved-...
— part 1: "Finding new comments". Video, + live demo if you click "Recent comments" in the upper right corner.
That's not very intuitive. It's easier to see new replies to comments one posts by going to the comments view on one's own user profile page, but seeing new replies in general is definitely not (especially if you don't check for several hours).
I think that traditional mail and news clients with their threaded view go it right for that purpose decades ago.
IIRC, HN does roughly the same thing that reddit does for deeply nested comments (meaning that you have to click on a link to view more of the thread). The most deeply nested thread I was involved in [1] on HN didn't appear to be handled any differently than any other thread I've seen here.
If it was indeed added later, this is an example of something Joel Spolsky cautioned against: don't do a huge marketing blitz for version 1.0 of your product. Aim for user count to increase in step with product maturity.
Though admittedly this might be hard to avoid with a product that has strong network effects.
Sounds like Nirvana to me. No more eternal “reply to all” chains that span months? I’m in.
1. Email lets you type an entire message before sending; IRC at least lets you type a whole paragraph, which is enough. Wave didn't let you type more than one character before sending.
2. The designers correctly realized chronological order isn't enough, you also want logical order, but unfortunately they provided the latter instead of the former, whereas you actually need both. (Gmail provides both: new messages and threads. Git provides both: view changes, and view current code. Google Docs provides both. Either view alone does not suffice.)
I would by all means encourage someone to take another shot at building something like Wave, with those problems fixed.