Don Caton said:
C'mon. First of all, Microsoft generates over $10 BILLION a year from
sales of Office, and Outlook is included in every edition of Office,
even the most basic, stripped down OEM version that's preinstalled on
many machines. If they increased the price of Office by one cent, they
could fund the addition of NNTP into Outlook many times over.
And what is their operating costs? Quoting revenue is the ploy of the
foolish. Yeah, they make a lot of money. They also spend a lot of
money. Doesn't matter that it is Microsoft. I don't see you asking
AMD, nVidia, and Intel to give you a free chipset on their mobos, or
Seagate to give you extra capacity on their drives without cost.
Quoting just your earnings is only half the equation (well, actually
less than half because besides expenses you also have taxes, too).
And when have you ever heard of a software company raising the price
of a product and attributing the increase to one particular feature?
Why do you think software developers add new features and then charge
for the upgrades or raise the price? Because of requests from users?
They want to continue the marketability of their product which means to
add new features even if they aren't wanted (but consumers can be conned
into thinking they want them). If they are requested in large enough
numbers then they add the feature knowing it is something they can
generate more revenue for it. Yeah, MS Office comes as a suite but you
can purchase the components separately, and do they cost the same as the
suite? Based on your logic, the price for the suite shouldn't cost more
than, say, Word alone because the rest is just added features to Word.
Add a whole other protocol, NNTP, then IRC, then RSS, then <keep going
through a wishlist>. You don't think all that added codebase is going
to drive up the cost of the product?
Despite its ever-increasing complexity and the cost to produce it,
software remains inexpensive relative to most everything else. You
can buy a copy of Office 2003 Pro for less than you could buy a copy
of WordStar 20 years ago.
So your argument is that the more features that get added then the
cheaper will be the price of the product? Very interesting economics
you suggest. I did not say that over time the codebase for the added
functionality would not be reduced in cost due to volume sales over that
long haul. But new functionality is something saleable. Old code wanes
in its saleability and thus it cannot maintain the same level of
pressure for sales hence its cost comes down. As the old code wanes in
saleability, its price would go down. So if Outlook became staid then
its price would wane. However, by adding new functionality, like NNTP,
IRC, RSS, a superior note function, and so on, then they can, at least,
maintain the price for the product. So instead of the product getting
cheaper over time, it maintains its pricing or increases. How much
would you pay for Wordstar today? The same or more than what you pay
for Word? Not likely. Old code gets cheaper over time, so to retain
marketability you inject new code. So you pay MORE to get the old code
plus the new functionality.
Outlook is a Personal Information Manager. If email isn't "personal
information", what is it?
Do some historical research on PIMs. They didn't have e-mail because
e-mail wasn't big not so long ago. The first time I saw a salesperson
using Act!, it didn't have e-mail. In fact, the first time I saw e-mail
in a PIM was in Outlook (but then I'm no wizard regarding every PIM
application that was ever available and their feature set). As e-mail
became a more viable and trustworthy communications venue then it got
added to PIMs. We aren't in disagreement here and are actually in
vehement agreement: e-mail has become important if not critical for
business. The point was that e-mail was and is seen as a business
communication channel. NNTP is not. NNTP is seen as play time by
employees and thus a waste of company resources but companies realize
that a certain amount on non-productive time is needed for their
employees and may tolerate NNTP, just like they tolerate web surfing
even if not work-related, or personal e-mails, and the coffee machine,
and gathering areas or a nice lunchroom, because it makes their
employees happy. But those equate to expenses to the company so they
have to weigh what expenses they want to incur and to what degree (i.e.,
do they get more than they pay).
Perhaps not for you, but not everyone has the same needs as you do.
It became part of my primary business activity when I started working
on a project with a few other programmers ...
See, you're off talking about a very small segment of the user community
for newsgroups and a very small portion of the corporate community.
Programmers, techs, developers, QA testers, and the like are not the
majority of users out there. Computer technology computers are not the
majority of corporations out there. If only the computer industry used
their own products then I would have to wonder if it would be a
sustainable industry. You don't sell to yourself to generate revenue
and growth.
That's a red herring. Unless you're trolling the binary groups
looking for porn or pirated software, the vast majority of newsgroups
articles are text only, without attachments.
And unless the company uses content filtering or operates their own
newsgroups server that is managed by them to eliminate the binary groups
(or has their ISP provide an NNTP for them with the restrictions) then
how does the company prevent their employees who have NNTP access from
visiting particular newsgroups? Once in, all in, everywhere in.
Obviously we all speak from our own experiences. I have not yet found
good evidence or studies made of all computer-using companies regarding
their attitude and leniency towards NNTP. We sell software to banks and
other financial institutions, schools, government, manufacturers, and
other large companies. At $80,000 a pop plus the cost per seat above
that, we get involved with them in beta testing or implementing our
software, so I've talked to quite a few sysadmins to find out what's
going on in their company. The ones that are computer technology
oriented do permit NNTP access, some freely and some choked, because
they have the local talent and expertise to protect themselves;
otherwise, NNTP is seen as a bane and usually gets blocked or severely
choked.
This is only for direct NNTP access (i.e., using the network news
transfer protocol itself) and not to letting employees access newsgroups
via a webnews interface, like Google Groups or Microsoft Communities. I
don't have enough info from my sysadmin contacts to know their attitudes
toward the webnews interface to newsgroups. I believe Google Groups
doesn't permit ANY attachments when posting nor can the webnews users
retrieve attachments for posts in binary groups. That makes the webnews
interface a much safer means of accessing newsgroups but at the cost of
severely reduced functionality, like not being able to flag threads to
watch, the lack of rules to killfile objectionable posters, no reading
of posts while offline, and several other features only available when
using an NNTP client. Safer access but less potent. I haven't seen
much, if any, resistance towards using webnews like I do against using
NNTP.
And if you should happen to download some malware, a properly
configured virus checker would trap it anyhow.
What, you think new variations or mutations don't get by anti-virus
scanners? Or past IPS'es (intrusion protection systems)? Why do you
think you have to keep downloading new signatures? Why do you think AV
software employs heuristics to catch *behavior* that might be indicative
of a virus or trojan? Because they know they won't catch everything
based on just the signatures of KNOWN viruses and trojan so they also
try to detect based on behavior but obviously the heuristic rules
themselves are limited in what behavior they detect.
If that's the case, then why does Microsoft provide the ability to
view newsgroups in Outlook when used in conjunction with Exchange?
Exchange is certainly not a product designed for personal use.
As noted above, some companies do permit NNTP access. I didn't say all
companies blocked it. My experience with sysadmins is that they
typically hate NNTP and have to take extra measures if it is allowed and
this incurs expense (in time, software, hardware, or other resources
which is often more expensive than any productivity gained therefrom).
You have evidence that indicates corporations actually relish providing
NNTP to their employees? I'd be glad to read it. I can only relate my
experiences in saying what I see happening so obviously it is a biased
opinion since I don't see everything, and neither do you. However, I
don't bias what is typical of corporate attitude and implementation of
NNTP based on my experience in a computer technology company with lots
of computer savvy users around here because that is not the norm. Your
realm of experience is different than mine. So if there has been some
studies regarding corporate NNTP access, how freely access is permitted
or how it is choked, then surely tell me about it.
We've already heard the past rumors that Microsoft was going to dump
Outlook Express. There was a huge wailing by users that wanted to
continue using OE. If Microsoft rolls NNTP into Outlook then they
probably will do that by rolling in the code from OE, if possible, into
Outlook. Then perhaps there would be no cost increment for adding the
new protocol to Outlook. At that point, since Outlook does the e-mail
function that duplicates the e-mail function of OE, and since Outlook
would then do NNTP, too, my guess would be is that if Microsoft puts
NNTP into Outlook then they won't need to continue to lose revenue on OE
and and OE will disappear. So all the freebie OE users lose and have to
find another freebie e-mail client. Microsoft would still be providing
NNTP support but then you would have to buy their commercial product to
get it. Sounds very much like something Microsoft might attempt by
pulling over a portion of the userbase of their free product for which
they generate no revenue, as would any corporate entity. Why would
Microsoft continue to lose on OE when they can make revenue on Outlook
after adding NNTP? Maybe they might continue providing OE but the
impetus to do so would be reduced. SpamNet was free until they decided
to go commerical and pull over that portion of their userbase willing to
pay for the product. Microsoft just changed Hotmail so users will have
to pay and, although some users will abandon Hotmail (or submit to
access only via the webmail interface), some will pay to continue to
have client-side access to their account.
I suppose they could implement NNTP as an add-in but there are already
products to do that. Sure, Microsoft could then contract with one of
those vendors to add NNTP to Outlook via a plug-in but, as you know,
that results in a crippled version of that 3rd party product. If they
bought the company to get the plug-in, they have responsibilities to
their shareholders to somehow offset that expense. They don't buy a
company so they can go out of business. So why pay Microsoft later when
and if they ever add NNTP functionality to Outlook when you can pay for
that now?