Posted on 10/04/2006 11:35:01 AM PDT by ShadowAce
"The long term effect will be that people, (college kids), who have switched to Linux at home because that's what they could afford, will begin to demand what they've used at home, at work."
That's a big reason why I switched over to Linux. The cost of buying Windows is a hugh turnoff given the ever-rising cost of tuition...
IIRC, Windows NT was based in large part on Microsoft OS/2 1.3 (OS/2 2 and up were produced solely by IBM).
In fact, WinNT 3.1 was originally designed to be released as OS/2 3.0.
Don't overlook the Rise of the Machine, the virtual machine.
Yes, painless Linux distros like Ubuntu will become popular as hosts for virtual servers. One copy of M$, legal or otherwise, can be duplicated endlessly.
Consumers will have a choice. Patch M$ on the first Tuesday of every month or open a new copy of the virtual, M$ appliance at your leisure, when necessary.
I like it too. I have my laptop setup to where I can boot to either XP Pro, Knoppix, or Ubuntu. I'm a big Knoppix fan, but find myself liking Ubuntu more and more every day.
I wouldn't be surprised if the EULA gives Microsoft the right to enter customer homes and inspect their computers whenever their software flags them as a pirate.
That's pretty sick. The advanced bells and whistles on OS X work fine with the Intel 950 integrated graphics chipset in the Macbook and Mac mini. As usual, Microsoft tries to copy Apple, but blows it.
Windows 1.x, 2.x and 3.x were just graphical shells on top of 16-bit DOS. Windows 3.x did give protected mode on capable processors, making an actual improvement over real-mode DOS.
Windows 95 -> 98 -> 98 SE/ME (based on 16 bit DOS)
Windows 9x was a hybrid 16/32 bit OS. It could run 32-bit apps in their own address spaces, but 16-bit apps got lumped together and thunked.
Windows NT was a 32 bit design written from scratch based on a blank-sheet architecture by David Cutler (architect of DEC VMS, which rocks).
While NT was written from scratch with a lot of influence from VMS, it had OS/2 influences too. It took a turn south when Windows 3.x was successful, because Gates decided to scrap the OS/2 API and replace it with a 32-bit version of the Windows 3.1 API. Since Microsoft loves backwards compatibility, there have been some major kludges since then to overcome this basic fact.
Windows 2000, written from a clean sheet but based on Windows NT.
Windows 2000 was just NT 5.0, some work under the hood plus putting a Windows 98 face on NT.
Windows XP, based on Win2000.
Some more work under the hood, plus some GUI pretties inspired by Crayola. Windows NT 5.1.
Vista, clean sheet based on XP?
More based on Windows 2003 Server (NT 5.2). Call it NT 6.0.
NT 3.1 was supposed to be OS/2 3.0--IBM was to develop version 2.0.
But the collaboration between MS and IBM fell apart, with MS continuing to develop Windows. IBM continued to work on OS/2, but it never took off aside from a small and loyal niche market.
So, MS took out the OS/2 API and much of the IBM code--replacing it with the Windows API and their own code. Technically it was clean-sheetede because MS wrote a ton of new code and put it around the new NT kernel, which MS implemented.
It is interesting how this history is discovered and recalled piece by piece, as if M/S doesn't care too much about it.
Classic Linux user thought process...
That it is.
And then to realize that there's only a handful of things that MS has made completely of their own innovation.
Interesting to think that Windows XP can trace its roots back to OS/2....
Thread Jester Ping
A low-volume pinglist dedicated for all the thread jesters out there--you know who you are...8^)
FReepmail rzeznikj at stout or MikefromOhio to be added or struck from the list...
hehehe!!
It gets better...
And the first time this hits a business computer and they have a certificate of authenticity, M$ is toast.
So I see!
Leaving aside the technical aspects of all this, is it legitimate to build software that cannot be run if it is pirated?
Oh, don't take everything so seriously.... =p
I think it's acceptable in principle, provided that it's fully disclosed in advance and the vendor takes full responsibility for damage caused by false triggers.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.