Posted on 09/13/2003 7:32:43 PM PDT by chilepepper
As far as the os that government pants after not being a good thing, the dept of homeland security just got spread-golden-eagled over their desks for MS, so you might not be far off. ;-)
From the looks of nearly all the posts on this thread, LINUX is WORSHIPPED on FR, NOT slandered. For my part, any OS that GOVERNMENTS pant after can't be all good.
I never said Open Source is the only way to make new stuff. I said it's a way that has worked. Maybe that doesn't fit into your economics, but some of us find it quite useful and even profitable.
Forget these little theories you "know." Reality matters more.
from this qoute . . .
to the point . . .
Linux is already available in 64bit versions (not XP), that Linux already has clustering capability (not XP), that Linux has a choice of over 4 desktops (not XP), that Linux can read HPFS, NTFS, FAT, UFS, DFS, and has a working version of a filesystem driven database-style transactional updates (not XP), and I could go on . . .
Innovation requires the FREEDOM to innovate.
This was a thread about linux and Microsoft. What does the concept of public domain have to do with either of those things? Why would you introduce that concept into this thread?
Linux is already available in 64bit versions (not XP)
Linux already has clustering capability (not XP)
Clustering has been available since NT 4.
that Linux has a choice of over 4 desktops (not XP)
Huh? I can think of a half-dozen drop in replacements for Windows Explorer off the top of my head. Here's one. Here's another one.
that Linux can read HPFS, NTFS, FAT, UFS, DFS
Just don't think you can write to an NTFS partition under Linux. Anyway, you can get drop-ins to read (and write) all of those under Windows, plus ext2, ext3, and a lot more.
and has a working version of a filesystem driven database-style transactional updates (not XP)
Not ready for prime-time. So does the next version of NTFS. If you want production-ready, BeOS had one five years ago.
Nothing wrong with preferring Linux over Windows, but it's usually wise to be aware of the actual facts first...
One of the ways that MicroSoft could handle this sort of situation is to begin releasing its code for the versions of its OS's that it no longer supports.
Consider: Windows 95, 98, and NT 4 are no longer officially supported. MicroSoft is no longer selling those OS's, yet MicroSoft still has the source code for all of the above.
So why not earn REVENUE, marketshare, and goodwill from that source code?! Windows 95 could become Open Sourced.
MS Windows 95 code could easily be placed online. Let anyone use it for free. Volunteer teams could readily be assembled, especially with MicroSoft's corporate direction and guidance, and open source versions of Windows 95 could begin being developed out in the wild.
Such releases could be free for everyone, with the caveat that reselling such new releases would have to cut MicroSoft in on 15% of the gross. For developers who don't resell such new enhancements but rather instead use them internally, there would be no cost.
Poof! In one easy step MicroSoft would own the open source market, would gain goodwill, would add a new revenue stream for obsolete software code that they aren't even supporting, and could win back customers such as Munich as well as stop new defections to Linux.
It would be tough to argue against open source MicroSoft, after all!
This move would also have the effect of dampening MicroSoft's current over-enthusiasm for obsoleting (i.e. ceasing corporate sales and support) their releases quite so fast. Bean counters in Redmond would push to extend corporate support (a needed action) rather than see perfectly good proprietary software on the open source fast-track.
Moreover, MicroSoft would have a new pool of code to dip into for innovations. Naturally MicroSoft would retain the rights to use any enhancements made by open source groups to its code, so when the occassional gem comes along MicroSoft will get to incorporate that new code for free into its new systems.
The alternative, of course, is to continue to lose market share to open source projects from competitors, as well as to continue to lose any benefit from their old, retired software code in their unsupported and now obsoleted software (e.g. Windows 95).
No, there are large numbers of players who would love to be able to have that source code, along with the rights to develop, enhance, and use. Most shelfware and large amounts of proprietary code still runs on Windows 95, you know.
Besides, if nobody wants it, what does MicroSoft have to lose? Make it Open Source.
At the very least MicroSoft can gain goodwill and have an irrefutable talking point for the Linux crowd; i.e. that anyone can develop on Windows 95 because we've just made it an Open Source code base.
And if some developer comes up with some outstanding enhancement or niche market for resale, then MicroSoft is going to get 15% of the profits (read: a **new** revenue stream).
Corporate goodwill, free development, and a new revenue stream all from software code that you freely admit is "dead."
How can you beat that tri-fecta?!
There's no downside. Windows 95 is already dead, so MicroSoft's copyright on that code is essentially useless already.
So why not allow an Open Source community to rally around that Windows 95 code base rather than Linux?!
My firm would take up the charge in a heartbeat, for instance. We'd love to be able to tell our clients that **we** could supply them with a Windows-compatible OS that we would be willing to support for them for as long as they desired.
Hell Yes we'd love to lock our clients into our proprietary version of Windows 95-on-steroids!
No, I'm suggesting that some money coming in from currently dead code is more profitable to MicroSoft than would be no money coming in.
Large commercial resellers of Open Source Windows 95+ systems would clearly pay MicroSoft a percentage of the gross rather than face lawsuits or jail.
What I'm suggesting is that MicroSoft allow there to become a "Redhat" for the very old, already dead versions of Windows (e.g. 95, 98, NT 4, etc.).
A "Redhat," mind you, that would be willing to pay MicroSoft 15%!
No, what I'm saying is let 3rd party companies provide such support and enhancements after MicroSoft reaches its own cutoff points/times.
Think about the movie industry. Hollywood first starts out with theatre releases, followed by pay per view cable sales, followed by DVD/video sales, followed finally by network TV releases.
I'm suggesting applying a very similar model to MicroSoft's sales. MicroSoft releases first, then supports it, then offloads it to a few preferred vendors, then finally makes it fully Open Source.
In contrast, MicroSoft currently kills the revenue stream from each release after a fixed time. Why? Why not follow the Hollywood movie model and continue to bring in revenue from old releases?
We have a winner!
Windows 95 is currently generating ZERO $$$ in new revenues for MicroSoft.
That's like burning the old movie reels after an early Hollywood theatre release instead of selling the movie on DVD or to TV.
Let firms such as mine have first crack at Windows 95. Earn revenue from them, and when they tire of it, release the code completely onto the Open Source world where at least MicroSoft can pick up a percentage of the resales.
Sell the movie on DVD and to TV. There's more to the release than just the big publicity and the glory release in the theatres!
Compare how many customers like Munich's 14,000 desktops you are losing to Linux versus what sending an old, dead OS like Windows 95 into Open Source would do.
Is Windows 95 really a threat to new MicroSoft OS releases?! I have a tough time swallowing that claim, anyway.
It's dead already. It's useless to Microsoft, so earn some revenue by following the Hollywood release model.
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.