|
Before continuing on to read my blog post, please check out the article from 2002 . Remember that back in 2002, the .NET Framework was 1.0, it was no longer in beta, but it was certainly not enjoying the same kind of traction that it enjoys today. ASP.NET was in its infancy and was struggling with a lot of problems, including performance and integration with non-Microsoft products (like allowing connections to the Oracle server).
Some assertions from this article that I find fascinating are:
So let this be a lesson to you kiddies, just because Microsoft says they're going to do something doesn't mean they're really going to do it :)
The really funny part of this is that I was googling around for information on ASP.NET and accidentally stumbled upon this article. When I read that Microsoft was going to announce shortly that they would be extending ASP.NET to Apache, I nearly squealed with joy... then I read the timestamp on the article. Damn you Google and your date-insensitive relevance algorithm!! Crap from 6 years ago should be completely irrelevant, or at least page 2 material :)
The fun thing is if you look in the source code of the dotnet framework,
you see a lot of checks in the Path.cs class for example.
// Platform specific volume separator character. This is colon (':')
// on Windows and MacOS, and slash ('/') on Unix. This is mostly
// useful for parsing paths like "c:\windows" or "MacVolume:System Folder".
//
public static readonly char VolumeSeparatorChar = ':';
public static readonly char VolumeSeparatorChar = '/';
As far as I know, their "Shared Source" implementation of the 2.0 Framework
was actually cross-platform capable. I know they had lots of lofty
intentions about making .NET cross-platform but I'm sure someone at
Microsoft responsible for world domination told them that openness and
sharing was bad.
I remember sitting in a Microsoft event in College in 2001 for the release
of the .NET framework. I remember a huge banner along the back of the room
saying that .NET will be the "cross-platform framework of choice for
today's and tomorrow's developers" (I have a photo of this banner in the
background, which is why I remember it).
It looks to me like Silverlight is a multiplatform implementation of .NET.
And Microsoft did wriite the Silverlight plugin for MacOSX/Safari.
How about that?
Microsoft said they were planning on implementing ASP.NET for Apache - and
they said that in 2002. Silverlight wasn't even a twinkle in anyone's eye
in 2002. Also, Silverlight v2.0 isn't a cross-platform version of the full
.NET, it's a semi-cross platform kinda-works browser-launched-only
plugin... A far cry from the cross-platform version of .NET that Microsoft
originally intended or led us to believe they intended.
Microsoft didn't have to do anything, Ximian and later Novell and the Mono
community did the porting for them. http://www.mono-project.com/ASP.NET.