Finally, speaking of overhead. BCM is truly an overheard and with almost no
integration with contacts. Do you really think adding newsgroup will
increase additional overhead to Outlook and why is it not for OE?
No, it would not "increase additional overhead". This excuse is often
thrown about, but having written a newsreader add-in for Outlook, I can
tell you it has absolutely no basis in fact. And I'm sure if you ask
the authors of any of the other newsreader add-ins, they will tell you
the same thing.
Outlook is basically a UI around one or more MAPI-compliant databases
(the .pst and .ost files). Things like emails, tasks, contacts, etc.
are simply records in one of these databases.
In order to send and receive messages or other items, Outlook loads
"transport providers". A transport provider is basically a DLL that
contains code that knows how to connect to a specific type of data
source, and how to read/write records in a MAPI database. Each account
you set up in Outlook is associated with a particular transport
provider.
To send and retrieve POP3 email for example, Outlook loads the POP3
transport provider. Outlook ships with transports for POP3, IMAP, HTTP
and Exchange servers. If you want to retrieve email from Lotus Notes,
you would install a Lotus Notes transport provider. Likewise for any
other information source that someone has written a transport provider
for.
In Outlook 2007, MS added the ability to retrieve RSS feeds and that was
done by writing a transport provider that knows how to connect to an RSS
feed.
To access newsgroups in Outlook, all you need is a transport provider
that knows how to connect to a NNTP server. If third-party vendors such
as myself can write one (using the horribly outdated and incomplete MAPI
documentation), there is no reason why MS couldn't write one too. And
the idea that this would add "overhead" to Outlook is simply absurd. It
would add no more "overhead" than the supplied POP3 transport does.
Outlook is slow, IMO, because it is based on MAPI, a circa-1993
technology that's overly complicated and all but obsolete. I'm a little
surprised that MS hasn't switched to SQL server databases by now, but
perhaps there is too much legacy and third-party code that would break
to make that practical.
And the premise that newsgroups are not useful and have the potential to
be abused in a corporate environment is equally absurd. I've sold a
number of site licenses to large corporations and I'm sure the other
newsgroup add-in vendors have as well. Employees can waste company time
on personal email and RSS feeds too, and Outlook has the ability to
connect to any web site so you can surf porn sites all day long without
ever leaving Outlook. Companies that are worried about this can block
access to HTTP sites, and they could block access to NNTP servers just
as easily.
As to why MS doesn't add newsgroup capabilities to Outlook, only those
folks within Microsoft who make those decisions know the answer to that.