Left the oppressive shackles of my Microsoft masters behind. Free at last, free at least, thank God almighty I'm free at last! Jeff Atwood echoed the sentiment he expressed sometime ago.
Sadly or gladly for us .NET developers, we still inhabits in this Microsoft Universe, from a long long time ago when IE6 was the king of browsers, and will still in the foreseeable future when all the cool kids will only role their eyes at the mention of anything Microsoft.
Yes, we are hopelessly brain-washed by Microsoft, its PCs, its office suites, its browsers, and most of all, its technologies.
Does anyone still remember Visual Basic for windows forms, or VBA, a flavor of Visual Basic, or VBScript the scripting language that were pretty widely used in ASP pages? Or ASP (short for Active Server pages), the once dominant server side language for generating web pages dynamically?
Then of course, suddenly it was nothing but .NET this and .NET that. The name at first sounded as bizarre as before iPad was unveiled, and caught fire in the tech world as fast as that iPad was embraced by the general public. And of course, all of us Microsoft devotees are transformed into visual studio users (despite or because of the hefty price tag).
I still remember the frenzy .net 1.0 caused and the cold sweat I had when I struggled to learn asp .net 1.0. As with typical Microsoft marketing (or marketing in general), the .net framework is filled with emerald gold with once impenetrable acronyms (CLR - common language runtime, CTS - Common Type System, BCL - Base Class Library), and is everything you need for complete success. Quoting from .NET official site:
the .NET Framework provides a comprehensive and consistent programming model for building applications that have visually stunning user experiences and seamless and secure communication.
Microsoft released .NET 1.0 and visual .net in 2002, and to this day, .NET framework and visual studio has gone through 7 major releases.
(From .NET Framework wikipedia)
Overview of .NET Framework release history
|Generation||Release date||Notes||Development tool||Distributed with|
|1.0||2002-02||original version||Visual Studio .NET||N/A|
|1.1||2003-04||first update||Visual Studio .NET 2003||Windows Server 2003|
|2.0||2005-11||rewrite of framework||Visual Studio 2005||Windows Server 2003 R2|
|3.0||2006-11||WCF,WPF,WF||Expression Blend||Windows Vista, Windows Server 2008|
|3.5||2007-11||LINQ||Visual Studio 2008||Windows 7, Windows Server 2008 R2|
|4.0||2010-04||parallel extensions||Visual Studio 2010||N/A|
|4.5||2012-08||asynchronous programming model||Visual Studio 2012||Windows 8, Windows Server 2012|
The 2002 ASP .NET web form release was a major shift from previous scripting languages, and it caused huge confusion among hapless little developers like me who tried plugged in code into the life cycle of an aspx page at the right moment. PreInit, init, preload, load, prerender, render ... I sincerely believed then I was too brain damaged to get it.
Now with the decline (possibly quick collapse) of PC era and all cool things about mobile, shall I say, .NET is desperately trying to catch up and accommodate?
One telling example is that the latest release of .NET 4 has not only the major .net languages C# .NET, VB.NET, F#.NET, it also includes a Dynamic Language Runtime (DLR) to allow languages like IronRuby and IronPython to run on top of .NET framework. This kind of adaptation can be seen elsewhere, visual studio has long included jQuery support, and it recently also started support GIT.
With the push of MVC since .net 3.5, Microsoft is now open about the sin of the original .net web form. It was cumbersome, it violated the fundamental development principal of separating presentation and data and a loosely coupled system.
Only if I knew or had a choice then.