From: "Joseph D. Wagner" <wagnerjd@prodigy.net>
To: "'Serge Kuznetsov'" <serge@wcom.ca>, <linux-kernel@vger.kernel.org>
Subject: RE: Is this going to be true ?
Date: Tue, 10 Dec 2002 18:05:24 -0600 [thread overview]
Message-ID: <001801c2a0a9$02613f40$2e863841@joe> (raw)
In-Reply-To: <050c01c2a091$77564600$9c094d8e@wcom.ca>
> I am just curious if someone has an opinion for the
> following link?
>
> Research Firm: Microsoft Will Use Linux by 2004:
> [trim]
Over Bill Gates' dead body. The Microsoft Corporation (and by that, I mean
the people running it: Chairman of the Board, CEO, CIO, CFO, Board of
Directors, most of the stockholders, etc.) is of the genuine belief that
Microsoft Windows is the operating system of the future. (Whether you
believe it or not is a separate topic.) Developing products for the Linux
platform is both 1) an admission that this belief was wrong, and 2) an
admission that their own current version of Microsoft Windows is somehow
shoddy, not-up-to-par, insufficient, or even on an equal footing with Linux.
The Microsoft Corporation will never admit either of those two things.
After all, it's the MICROSOFT CORPORATION. If they didn't believe these
things, they would go somewhere else.
The following scenarios are far more likely.
1) Future development of the Windows operating system or some of its
components will be *BSD based. The Microsoft Corporation will never touch
Linux. Period. The lawyers simply wouldn't allow it. The lawyers think of
GNU GPL as an infectious disease, and so anything Linux is out of the
question. The BSD license is far more favorable to proprietary development,
since it allows you to close off the source. Hence, assimilating a *BSD
structure, component, or piece of code is far more likely.
In fact, Microsoft Windows 2000/XP already did that with Kerberos.
2) Lower prices for Microsoft Licensing or more broadly interpreted
licensing. It may be that to better compete with Linux that Microsoft
lowers the prices of some of its Microsoft products.
One thing Microsoft has already done in this regard is to change the
licensing on Terminal Server. On Windows NT 4.0, each copy of Windows NT
Workstation needed a Client Access License and a Terminal Server Client
Access License to connect to a server and a server's Terminal Server,
respectively. Now, with Windows 2000 and XP Pro, a Terminal Server Client
Access License is included with either a regular Client Access License or a
Windows 2000 or XP Pro operating system license (I forget which).
3) Develop kits, wizards, and other software to help people convert from
Linux to Windows. Microsoft already has Unix for Windows Services (or
something like that with a similar name). It's purpose is to help people
convert from SCO UNIX to Windows. I see no reason that Microsoft can't
develop a similar such kit for, say, Red Hat Linux. (Sure, it would be one
heck-of-a-kit and very complicated, but I can see it).
*Sigh* Yet, another topic for the linux-politics list. There is no such
list, BTW, but this email highlights the need for one.
Joseph Wagner
next prev parent reply other threads:[~2002-12-10 23:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 21:03 Alteon AceNIC Coper Seen as Fibre ? (and incorrect settings) Stephan van Hienen
2002-12-10 21:16 ` Is this going to be true ? Serge Kuznetsov
2002-12-10 22:14 ` Herman Oosthuysen
2002-12-10 22:21 ` Serge Kuznetsov
2002-12-11 0:33 ` Michael Melanson
2002-12-11 0:55 ` David Schwartz
2002-12-11 1:04 ` Larry McVoy
2002-12-11 23:47 ` Henning P. Schmiedehausen
2002-12-11 0:05 ` Joseph D. Wagner [this message]
2002-12-11 1:08 ` Herman Oosthuysen
2002-12-11 15:55 ` Måns Rullgård
2002-12-11 16:33 ` Richard B. Johnson
2002-12-12 0:01 ` Henning P. Schmiedehausen
2002-12-12 3:16 ` Richard B. Johnson
2002-12-12 3:39 ` Mark Hamblin
2002-12-13 9:18 ` David Schwartz
2002-12-11 23:57 ` Henning P. Schmiedehausen
2002-12-12 9:22 ` Ragnar Hojland Espinosa
2002-12-12 14:15 ` Adam H. Pendleton
2002-12-12 21:24 ` Kjartan Maraas
2002-12-12 9:35 ` Helge Hafting
2002-12-11 13:41 ` Rik van Riel
2002-12-11 14:17 ` Måns Rullgård
2002-12-11 17:06 ` Serge Kuznetsov
2002-12-11 17:26 ` Roy Sigurd Karlsbakk
2002-12-11 22:01 ` john slee
2002-12-12 10:13 ` Måns Rullgård
2002-12-12 10:16 ` Måns Rullgård
2002-12-12 11:12 ` Henning P. Schmiedehausen
2002-12-12 13:19 ` Billy Harvey
2002-12-12 13:30 ` Henning P. Schmiedehausen
2002-12-13 10:56 ` szonyi calin
2002-12-13 13:19 ` Billy Harvey
2002-12-11 17:12 ` Serge Kuznetsov
2002-12-11 17:21 ` Alvaro Lopes
2002-12-12 6:50 ` Kai Henningsen
2002-12-11 17:29 ` Dave Jones
2002-12-11 17:18 ` Serge Kuznetsov
2002-12-11 13:38 ` Richard B. Johnson
2002-12-11 16:19 ` Alan Cox
2002-12-10 21:41 ` Alteon AceNIC Coper Seen as Fibre ? (and incorrect settings) Eric Weigle
2002-12-12 22:00 ` Jes Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001801c2a0a9$02613f40$2e863841@joe' \
--to=wagnerjd@prodigy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@wcom.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox