Corel-Microsoft Deal Means Potential .NET for Linux
Thanks to Scott McNeil for pointing out that in the SEC filing concerning the recent Microsoft investment in Corel that it grants Microsoft the /option/ for the next three years to have Corel port the .NET framework or portions by assigning at least 20 full time developers and 10 full time testers - or the equivalent thereof. Now, it is an option, but that's interesting that it's in there. It's Point 3 of the section I linked to.
The more I read about .NET, the more I like it. The commonly advice "use the right tool for the job" seems to suggest using something exactly like .NET and its CLR. In a large project, ML may be the best tool for some portions, JAVA/C# for others, and maybe C++ for still other portions. With the CLR, it's easy to pick the best tool for the job. This is reason enough for me to investigate it a little further and hope for something similar on Linux.
-ec
Believe me, I am the closest thing to a Microsoft fan/apologist that you will find on Slashdot. I am not bashing .NET simply because MS makes it; I am bashing .net because it, combined with Passport, will give MS far too much access to users' personal information.
.net, Microsoft will not only be able to track user behavior across its web network, it will have a comprehensive database of every Windows user's preferences--right down to what wallpaper he uses on his desktop.
Hotmail alone has 60 million registered users. Windows sells hundreds of millions of copies. With
The registry concept was pretty cool, because it allowed network administrators to standardize and modify desktop configuration settings remotely. That was a good feature that MS developed. However, putting this power in the hands of MS or malicious Internet users is not a good feature. Besides, MS has no right to compile a database of my preferences simply because I use Windows.
ByteMyCode.com: A Web 2.0 code sharing community.
Just so you know....
I don't care if it runs on Windows, Linux, or the next create OO operating system. I ain't gunna use it.
.NET?
"Sorry, the server hosting your documents directory "Business Plan" is temporarily unavailable. Please try back later. We apologize for this inconvenience."
All I am saying is that if Microsoft can't provide a simple, stable web mail service, how can we expect them to reliable handle the complex architecture they have layed out in
-josh
.NET, like Java, is an attempt to provide an appliation framework for the internet. With only 30%-40% or so of internet servers running on Microsoft platforms, they have to port the server side of .NET or it will die on the vine. (Unless, of course, they are arrogant enough to think that the mere existance of .NET will instantly bring them to 100% server market share.)
.NET).
On the client side, it is also to their advantage to port it because this will give them credibility in competetion with Java. The fact that they will be releasing the C# language specification to an open standards body unfortunately already gives them a head start on the credibility. Client side support for other platforms also means they can extend their Office monopoly onto other platforms without having to port it more than once (to
Despite all this, however, you can likely count on the Windows implementations being much more optimized, at least at first, and they will use this as leverage to try to increase there presence on the server side, where it currently lags more.
Corel's original OfficeSuite 8 was developped in Java and now that the Java VMs and average processor speeds are adequate to support it, they have the experience (and a codebase to start from,) to build M$ .NET and propagate it beyond the x86 architecture, something which M$ has repeatedly and demonstrably failed at.
But M$ file formats are locked tight and get changed every time M$ needs some cash.
If we can't obstruct, we can at least RESIST!
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
Does Corel have any experience in developing compilers, VMs, or systems libraries? This is a far more complex problem than making slight additions to the WINE project that had already been in progress for years before Corel came along. If Corel takes a lead role in the production of Linux.NET (which, luckily, I think is already trademarked by someone else), the results will be a farce, especially since so many of their best developers jumped ship during their incredibly-prolonged financial troubles.
I'd much rather see people like Borland, Tower Technologies, Appeal Virtual Machines, and SGI, who have the necessary skills and resources, take the initiative. But I guess there's not a lot of reason to make sure Linux has a GOOD implementation of
--JRZ
I am no Microsoft fan, but bashing .NET just because it's from them is very short sighted. Some of the ideas are very intersting, for instance common binary data types. This allows different languages to cooperate without the requirement of complex (slow, hard to understand) arbitration methods such as COM or CORBA.
Remember, people use computers to get things done, not to show off their latest window mamangers. If Microsoft make it easier to tie tools together people will use Windows and put up with its tempremental behaviour. Believe me, I've seen it where I work.
What benefit could MS hope to gain from .NET on Linux? It certainly would not benefit it to have Linux servers holding a significant part of the .NET server market - unless of course it all ends up with a closed-protocol and closed-source project and they can charge mega-$ for it.
On the client side though it might be a significant benefit for MS as the Linux desktop market grows to have .NET connectivity from a market penetration point of view. If MS holds the reins of power on the server end of .NET, and .NET clients become ubiquitous, it gives another market stranglehod to MS. That strikes me as the desired business direction - .NET servers running MS Software on an execlusively MS platform.
Cheers,
Toby Haynes
Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
This is simply a way for Microsoft to leverage Linux. If Microsoft controls the back-end, does it matter what the front end is? Gates knows that Linux is becoming more popular. Unlike other competitiors which he could simply buy or drive out of business, Linux represents an amorphous target that simply can't be hit. Porting .NET to linux is nothing more than a method to turn Linux his own advantage.
.NET on any platform." But what about all the clueless users that projects such as KDE, Gnome, and especially Eazel are working to attract? Do they understand that by using .NET they're giving even more power to a man who thinks he is the reincarnation of Napoleon Boneparte?
Now you might be saying to yourself that "I would never use
Its just embrace and extend all over again. Assuming of course that this is something they truly intend to do. I think whether they do it or not has a lot to do with how much of an inroad Linux makes into the clueless desktop user market. The more lemmings use Linux, the more likely Microsoft is to do this.
Lee Reynolds
Muslim community leaders warn of backlash from tomorrow morning's terrorist attack.