Spiros Bousbouras said:
In what way is a newsreader interface for reading better than Google
groups ?
1. It's much more responsive, particularly if you either (a) have a
local news server (though setting up a news server is a serious
undertaking for a beginner) or (b) your newsreader supports
collecting news in bulk. Google Groups makes you fetch a few
articles at a time, and then collect the next bunch and so on.
2. Threading seems much better in real newsreaders. Google Groups
shows you even fewer articles at a time if you turn on the tree
view -- and it doesn't provide a particularly helpful view of the
thread, and doesn't tie up to the individual articles very well.
3. At least for me, Google Groups randomly collapses a selection of
articles which is a major nuisance when I'm reading through an old
thread. Newsreaders don't do this stupid thing.
4. Killfiles, so you don't have to wade through piffle posted by
idiots like me if you don't want to. If you get a vaguely fancy
newsreader, you can score up articles which interest you
especially, e.g., follow-ups to your own messages and their
descendants, or articles posted by people you find particularly
interesting.
5. Major bonus for me: I get to use a proper editor for composing
messages, rather than the crappy multiline widgets you get in web
browsers. (You don't think I word-wrap these indented paragraphs
by hand, do you? ;-) )
It comes down to this: a newsreader is a specific tool, honed for the
job of reading news. It's capable of providing a user interface which
makes reading news pleasant and efficient (though different news readers
have different ideas about how to do this -- pick one that suits you,
'cos there are lots out there). Anything web-based has to make
compromises in order to fit into the limitations of web browser
interfaces.
This is all off-topic for comp.lang.c, so I'll not respond on this
thread again.
-- [mdw]