MSDN... WTF?



  • http://msdn.microsoft.com/winfx/default.aspx?pull=/library/en-us/dnlong/html/netfx30.asp

    For those out there that, like me, are still trying to get to the end of the .net 2.0 that just get out of beta status a few months ago.

    (There are extra points for finding the circular references on the article)

    And just to have other people opinions: what do you think of "Project LinQ"

    My opinion (I like to give my opinion before hearing others to demonstrate that I'm no coward ;)):

      LinQ only gives each folk a tool for doing what any programmer that works a lot with (pick the ones that best suit you) Collections/XML/DataSets should do in order to get the job done. The standarized use of LinQ in .Net environments can make the code easier to read.

      Maybe I'm missing something but, for what I had read, LinQ is no more than a set of iterators over a group of common structures; I have done similar things and added them to my personal library that gets carried away from project to project, maybe I can erase some of the code of the library and replace it with LinQ calls, time will show.



  • Read this: (directly from Microsofts referenced website)

    """

    About Microsoft .NET Framework 3.0

    The Microsoft .NET Framework version 3.0 (formerly known as WinFX) is the new managed-code programming model for Windows. It combines the power of .NET Framework 2.0 with new technologies for building applications that have a visually compelling user experience, seamless communication across technology boundaries, and support for a wide range of business processes. Microsoft plans to ship .NET Framework 3.0 as part of Windows Vista. At the same time, Microsoft will make .NET Framework available for Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1.
    """

    Doesn't seem to be that big of a WTF anymore, does it?



  • Maybe my position wasn't clear: I said WTF when I saw it they are teaching how to deploy a technology that is in Beta status (Beta to say something as there is no proper ".Net Framework 3.0 Beta" for download in the MS website); also this leads me to the second point that is that they are teaching how to deploy technology that isn't ready to download so:

      - If the technology is ready for deployment -> do a proper release

      - If you don't do a proper release -> why do you teach how to deploy it?

    My first thought when I started to read the article was: "deploying .net 3.0? they finished it? so soon?", then I took a look at other MS webpages and the answer was: NO they didn't finish it yet; so I thought "WTF?"



  • The naming convention is a little bit odd. They say themselves that .NET 3 is .NET 2 with extra stuff added.



    "The .NET Framework 3.0 shares many components with .NET Framework 2.0,
    and the common language runtime (CLR) and base class libraries are the
    same as those in .NET Framework 2.0
    . Therefore, these shared components
    stay at version 2.0."




    .NET 2 SE or .NET 2.5 might have been a better name.




  • Linq = Language Integrated Query, that says it all

    Linq will come in the version after 3.0. Linq is just some of the new parts, you should also look into DLinq and XLinq (http://msdn.microsoft.com/data/ref/linq/)

    The great thing about linq is, that it is easy to implement it in your own projects.

    For a sample:
    http://weblogs.asp.net/scottgu/archive/2006/06/04/Using-DLINQ-with-ASP.NET-2800_Part-2-of-my-LINQ-series_2900.aspx

    About .net 3.0, it has been discussed and explained many times, gooogle it up :-)



  • @RayS said:

    The naming convention is a little bit odd. They say themselves that .NET 3 is .NET 2 with extra stuff added.



    "The .NET Framework 3.0 shares many components with .NET Framework 2.0,
    and the common language runtime (CLR) and base class libraries are the
    same as those in .NET Framework 2.0
    . Therefore, these shared components
    stay at version 2.0."




    .NET 2 SE or .NET 2.5 might have been a better name.




    Maybe the next version (that would rightly involve a major version number increase) will skip one.  So WinFX become 3.0 and what should have been 3.0 will be 5.0.

    First shalt thou take out the Holy Pin. Then, shalt thou count to
    three. No more. No less. Three shalt be the number thou shalt count,
    and the number of the counting shall be three. Four shalt thou not
    count, nor either count thou two, excepting that thou then proceed to
    three. Five is right out. Once the number three, being the third
    number, be reached, then, lobbest thou thy Holy Hand Grenade of Antioch
    towards thy foe, who, being naughty in My sight, shall snuff it.



  • @Taliesin said:

     

      - If the technology is ready for deployment -> do a proper release

      - If you don't do a proper release -> why do you teach how to deploy it?

    By not doing a proper release, they completely cover their butts. Observe these two situations:

    1. "Hey, I used your autoupdate and it erased my database. Then it emailed my customer list to a Chinese spam house."

    2. "I followed your complicated beta installation instructions. Your beta version erased my database and emailed my customer list to a Chinese spam house."

    Unfortunately, betas are now the SOP for a lot of software companies. Once they started making software "as is", it didn't take long for a lot of companies to cut the QA departments down to a minimal level and let the paying customers do their testing. It's under the guise of "beta", so failures are accepted by the consumer. Those failures are tolerated because your version number is higher than someone else's, so you're better than they are and you win.

    This "beta" mindset is, in my mind, the root cause of all bad code. If consumers wouldn't tolerate failures, we wouldn't have Johnny "Alphabet Soup Degree" Codemonkey grinding out crap and calling it chocolate. Hey, it's not like anyone's ever died from a software bug. 

    Of course, if you give the idiot masses what they want, you'll get rich. Just ask the Waltons.



  • Microsoft never gets it the first time, but after 6 or 7 major releases, they start to zero in on what it needs to be and how it needs to be. Linq 2.x is a bit soon for MS to have the kinks out. Personally, I'm waiting for Web 7.0



  • @RayS said:

    The naming convention is a little bit odd. They say themselves that .NET 3 is .NET 2 with extra stuff added.

    <font size="5">H</font>eaven forbid that MS takes something out of a new release...Like the kitchen sink.



  • WinFX will be .Net 3.0, LINQ and other codename "Orcas" stuff will be .Net 3.5.

    I recommend you watch this video, it clears it up a lot.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.