Slashdot Mirror


Microsoft Drops .NET Name For Next Windows Server

metamatic writes "C|net is reporting that Microsoft is dropping the name "Windows .NET Server" and going back to "Windows Server 200x" (where x is currently expected to be 3). Other products with .NET in the name are also being evaluated for renaming. Analysts are being quoted as saying that slapping .NET on so many Microsoft products has confused people as to what .NET actually means. Or could it be that customers know what it means, but nobody wants to buy it?" Obiwan Kenobi points out a similar article at ENT News

406 comments

  1. This is hardly news... by bwalling · · Score: 1, Redundant

    They are changing the name because people are getting confused about what .NET really is. It was a bad idea for Microsoft to try to add ".NET" to every single product they sell.

    1. Re:This is hardly news... by Anonymous Coward · · Score: 0

      "They are changing the name because people are getting confused about what .NET really is. It was a bad idea for Microsoft to try to add ".NET" to every single product they sell."

      Hey thats news to me.
      Ya know what isn't news to me, the fact that Microsoft is bad for America, thats just a fact my friend.

    2. Re:This is hardly news... by jerkychew · · Score: 1

      I still don't know what the hell .net is supposed to be, and I like to think I'm at least a little technical...

    3. Re:This is hardly news... by MonTemplar · · Score: 4, Interesting

      Actually, I think it's more like what they did when they changed Windows NT 5.0 to Windows 2000 - hoping to ditch all the bad news (mainly delays in getting to a working product) associated with the former name.

      --
      -MT.
    4. Re:This is hardly news... by Anonymous Coward · · Score: 1, Funny

      Let's see..you're reading a news site. The story was posted on the front page of said news site. It's a recent announcement, from -another- news site.

      I guess my only question is, what the fuck qualifies as news to you?

    5. Re:This is hardly news... by DaytonCIM · · Score: 5, Insightful

      Good point. Going one step farther... I believe that Microsoft never got behind .NET. Sure, there was a mild push last year, but then *poof* no more push.

      They had really pretty sections in most book stores for the VAST number of .NET books, but really there was never a "Microsoft type" marketing push. Maybe because there wasn't a "product" to push? .NET RIP 2003

    6. Re:This is hardly news... by silicon_synapse · · Score: 3, Interesting

      From the article:
      Analysts are being quoted as saying that slapping .NET on so many Microsoft products has confused people as to what .NET actually means.

      Your comment:
      They are changing the name because people are getting confused about what .NET really is. It was a bad idea for Microsoft to try to add ".NET" to every single product they sell.

      Where's +5 Insightfull coming from?

    7. Re:This is hardly news... by HiredMan · · Score: 5, Insightful
      when they changed Windows NT 5.0 to Windows 2000 - hoping to ditch all the bad news

      Actually I think this was also the first real push made by M$ to go to leased software.

      Naming your Word Processor or Office Suite after the year makes no sense at all unless you plan to release a new one every year like they do cars. They get rid of the Y.X naming - which actually provides information to the consumer if you use it correctly - and start getting people used to naming like "Word 2000".
      That way it seems more natural when you pay for Word 2003 and then pay again for Word 2004 then next...
      Cause it better you know... the numbers bigger...

      =tkk

    8. Re:This is hardly news... by squiggleslash · · Score: 4, Informative
      You know what Java is? Language, virtual machine, libraries, etc? Create apps that will "run anywhere", and an environment which is a kind-of networked execution infrastructure?

      .NET is an attempt to do the same thing. Not a clone of Java, but like DOS and CP/M, or Windows and MacOS, etc.

      If I were in marketing, I'd say both .NET and Java are attempts to build operating systems for the Internet (as opposed to operating systems for computers.)

      --
      You are not alone. This is not normal. None of this is normal.
    9. Re:This is hardly news... by Stonent1 · · Score: 1, Offtopic

      From the article: Analysts are being quoted as saying that slapping .NET on so many Microsoft products has confused people as to what .NET actually means. Your comment: They are changing the name because people are getting confused about what .NET really is. It was a bad idea for Microsoft to try to add ".NET" to every single product they sell. Where's +5 Insightfull coming from?

      I said the same exact thing and if my mod points hadn't just run out 2 hours ago, I would get this message out of troll status.

    10. Re:This is hardly news... by AKnightCowboy · · Score: 5, Insightful
      Actually, I think it's more like what they did when they changed Windows NT 5.0 to Windows 2000 - hoping to ditch all the bad news (mainly delays in getting to a working product) associated with the former name.

      Hey, I have an idea. Now, this is going to sound kind of crazy and I know I'm a little ahead of my time, but what if we were to simplify the name and give it a meaningful version number? We could call the next released version Windows 7.0. Microsoft Windows 7.0. It could be a HUGE media frenzy! "No XP, no 2000, no .NET.. just 7.0. The added benefit is that when a new upgrade comes out we can name it Windows 7.1 and people can tell that it is a NEWER and more advanced version!"

    11. Re:This is hardly news... by freeweed · · Score: 3, Insightful

      I thought that's what C# was all about - cloning Java.

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    12. Re:This is hardly news... by LinuxCumShot · · Score: 1

      no, that's C# and the CLR which are part of .NET .NET is much more... body nobody knows how much more.

      --
      -- OMFG = Oh My Floatse Goatse
    13. Re:This is hardly news... by timeOday · · Score: 2

      Besides the confusion factor (which is large), 'e'-this and '.com'-that have gone out of style completely. Everybody is mad about their e-stocks dot-bombing, so naming things after the Internet would be dumb now.

    14. Re:This is hardly news... by squiggleslash · · Score: 3, Interesting
      C# is analogous to the Java language. The CLR (or is it CIL? Or CLI? I can never quite remember) is analogous to the Java byte-code, etc. .NET is basically the all-encompassing name for the whole thing.

      Remember that Java is a language, a plug-in, a virtual machine, and half a dozen other things. Ironically, Microsoft's difficulty at explaining what, exactly, .NET is, is despite the fact that they've done a better job of breaking it up into seperate, easily named, modules, unlike Sun who have generally called the whole thing "Java" (well, ok, they've called different Java bundles things like J2EE, J2SE, J2ME, Java2, JavaOne, etc..., but that's another story.)

      Maybe someone should go the extreme opposite and create a language/VM system called "*grunt*".

      "What's the VM called?" *grunt* "Well, ok, what's the language?" *grunt* "Ok, what's the marketing term for this?" *grunt* "Geez. Ok, what's the classname for a window?" *grunt*...etc... you get the idea.

      --
      You are not alone. This is not normal. None of this is normal.
    15. Re:This is hardly news... by rseuhs · · Score: 4, Informative

      .NET is like Java, but it only runs de-facto on Microsoft platforms (in theory it will run on BSD too, but important parts are missing)

    16. Re:This is hardly news... by Schnapple · · Score: 5, Informative
      but really there was never a "Microsoft type" marketing push. Maybe because there wasn't a "product" to push?
      Well there was the .NET framework, the free C# and VB.NET compilers, and Visual Studio .NET - four products. All but one free. And of course there were the ECMA ratified C# and CLI standards. .NET is "something" and if you still don't get that Windows .NET Server was not all ther was to .NET you clearly haven't been reading some of these highly moderated comments.
    17. Re:This is hardly news... by JWSmythe · · Score: 4, Interesting

      Imagine that. If you're using say an OS called Microsoft Server 0.1 for your servers, and Microsoft Workstation 0.1 for your workstations.. Then if you saw that MS Server 0.2 was available, you'd know it was the next logical step in the upgrade path..

      I'm still a wee-bit confused by the currently available OS's..

      Windows 2000 (Professional|Server|Advanced Server|DataCenter Server)

      Windows ME

      Windows CE (CE||.NET)

      Windows XP (Professional|Home Edition|Media Center|Tablet|Embedded)

      Imagine if they just had workstation and server, with nice numbers. I'm still not sure what I'd be running all my servers on, if I went to MS.. Luckly, I don't have to decide. I put the same version of Slackware on everything, and just install the parts I need.. Funny, it all fits on one CD, and I don't even have to pay outragous licensing fees for each version, or packages I add on. :)

      I'm just sad that Slackware hasn't released a distribution for handhelds.. But lucky, "familiar" works on my iPaq.

      Every software I've seen uses logical version numbers, except Microsoft.. And they used to even do it.. Well, kinda..

      Win3.0
      Win3.1
      Win3.11
      Win95
      Win98
      Win2000

      The jumps in numbers are just too big.. Forget the subrevisions. Build numbers. SP numbers.. I feel sorry for the Microsoft techs who have to take tech calls from people who only know "I use Windows." When friends of friends call me and tell me that, it's like pulling teeth to find out if it's Win98 or XP.. "It came on the computer, how am I suppose to know?"

      --
      Serious? Seriousness is well above my pay grade.
    18. Re:This is hardly news... by agentbuzz · · Score: 2, Interesting

      We know that Microsoot wants to destroy the IETF, and that they seldom write RFC-compliant software (witness their implementations of Kerberos, DNS, and just about any other Internet protocol that you care to name).

      Remember that Microsoot's marketing efforts eclipse everything else that they are supposed to be doing...

      The first time I saw the expression ".net" in print with reference to an MS API, I thought,"These bastards think they are going to appropriate a TLD that is given only to elements of the Internet's backbone!"...

      ".NET is symbolic of the oracular "insight" of ownership of the Internet envisioned by MS employees who've done too much of the Brown Acid(tm)!"

      I still suspect that ".NET" was a symptom of a form of blindnes afflicting those who sincerely believe that they are God.

    19. Re:This is hardly news... by JWSmythe · · Score: 2

      I still haven't figured it out either. In one of our offices, we went on a quest to try to figure the thing out.. We contacted a few MCSE's..

      The most concise answer we found was ".NET is a framework." A framework for what, we don't know. I saw references to letting servers communicate, so is it a protocol? How about the .NET language variants? Is it a programming language? I read that .NET would let password databases be shared. So it's an authentication scheme? .NET will let you run applications on any platform, even non-Microsoft. But it was only Microsoft products tagged with the .NET name. Can I use 'vi' to write in the .NET?

      The most productive thing I ever heard about in .NET was a game that would let you play with players on other systems, using programming to tell your pieces how to move.. But even that didn't make too much sense.. I wanted to try it out, but at the time, it wouldn't run on Win98, and definately not on my Linux machines.. I'm not going to invest in a new machine, or sacrifice a server, just to install 2000 or XP to play a game.. The boss probably would frown upon that. Well, and people may be a bit upset. :)

      --
      Serious? Seriousness is well above my pay grade.
    20. Re:This is hardly news... by Anonymous Coward · · Score: 0

      Every software I've seen uses logical version numbers

      You must be pretty blind then. There is a ton of software that started using the version numbers and then switched to dates. Microsoft might be the first to mix and match letters and numbers, though.

    21. Re:This is hardly news... by yuiop · · Score: 0

      This game is called terrarium and is rather cool. You write the code for a creature that is then run on everyone else's machines (safely) and competes for resources. It looks good even if you don't want to write your own creature.

    22. Re:This is hardly news... by t0ny · · Score: 1, Interesting
      yes, MS is kind of confusing people already with XP.


      I wish I had a dollar every time I was talking about Office XP and someone thought I meant Windows XP.


      I think one of the problem is that, honestly, most people DONT know what .NET is. Its really pretty cool, IMO. But as with all technical things, there is a ton of misinformation amongst the tinkerers and charlatans.


      Thats ok, because it all just makes me look good when some doofus cant get it to work!

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    23. Re:This is hardly news... by Talez · · Score: 1

      Brilliant idea...

      Except the next version of Windows (Longhorn) is either going to be 5.2 or 6.0. I'm pretty sure it's 6.0.

      Windows XP is still version 5.1 internally.

    24. Re:This is hardly news... by Anonymous Coward · · Score: 0

      Every software I've seen uses logical version numbers, except Microsoft.

      I there is a company called Apple that has something called OS X or something. Have you ever used Netscape 5?

    25. Re:This is hardly news... by xtinct · · Score: 1
      no, that's C# and the CLR which are part of .NET .NET is much more... body nobody knows how much more.

      and you just missed a golden opportunity to enlighten us all...

      from what i gather, it is microsoft's attempt to steer development off of MFC, dll hell, and the rest of the things (backward compatibility, baby!) that make developing on windows such a pain in the ass.

      i think there's some built-in RPC type stuff via SOAP and of course the muli-language-single-bytecode thing that seems to get some people's panties in a bunch.

      a lot of the serf's find a lot of oooohh cool with .NET, not realizing that many of us have been doing these things for quite awhile... so it gives them the green light and the happy MS-approved stamp...

    26. Re:This is hardly news... by Anonymous Coward · · Score: 0

      The source code for Netscape 5 was released, but the code base was in bad enough shape that it was largly trashed. Since the result of the Mozilla project is only distantly related tot hat old source code, it made sense to name the next version of Netscape 6.

    27. Re:This is hardly news... by Anonymous Coward · · Score: 0
      I believe that Microsoft never got behind .NET. Sure, there was a mild push last year, but then *poof* no more push.

      I think you're simply wrong. MS marketed everything under the sun with the .NET moniker; in fact, their senior execs went so far as to say they bet the company on .NET. Turns out the unified marketing effort was a failure, but assuredly many of the products will be successful.* Passport aka .NET Services, the first casualty, was a dismal failure because no corporate IT departments wanted any part of it; and quite simply it's a loss leader at best in the consumer space.

      * For example, they already have bet their entire software development model going forward on the .NET Framework, from handhelds all the up to server-side apps. Yes the old C/C++ Win32/MFC/etc. runtimes are still there and won't go away anytime but for "enterprise" development (I hate that term), .NET is already quickly pushing aside the old Windows DNA framework and we're only (a little more than) 1 year in. Corporate software development is the real gravy train, and ground zero of the legal (and commercial) battle with Sun.

    28. Re:This is hardly news... by Anonymous Coward · · Score: 0

      The "X" is pronounced "ten". It's a roman numeral.

    29. Re:This is hardly news... by angryargus · · Score: 1

      Makes sense, although MS still hasn't got it right in practice. The last time I looked, "Works Suite 2003" was shipping with "Streets & Trips 2002".

      S&T hardly changes, so it boggles the mind how MS could miss the schedule for including S&T 2003 in the suite.

    30. Re:This is hardly news... by plover · · Score: 5, Informative
      and you just missed a golden opportunity to enlighten us all...

      Fine, then I'll do it.

      .NET the "language" is an intermediate language bytecode called IL (Intermediate Language). You can produce it from any .NET compiler. The bytecode that is "JITted" (Just In Time compiled) at runtime as needed. The runtime environment is a process called the CLR (Common Language Runtime.)

      .NET the framework also contains the system class, which exposes all of the available platform functionality. Those of you who use the Win32 API, Platform SDK, DDK, etc., know just how big this class is. It's fairly well organized.

      The biggest advantage to the platform for develpers is absolute type declarations with full knowledge at the object interface: if you write an object method in VB.NET that takes two Integers, a String, and an array of Dates and returns an Integer value, then you can directly refer to that method in your C# routine. There is no conversion needed between types, not even between languages, which has historically been a problem with Microsoft code ever since OLE.

      .NET also fully supports exporting and importing these objects via SOAP.

      Visual Studio .NET is a development IDE for all the Microsoft .NET languages: VB.NET, C#, and others. It's similar to Microsoft's Visual Studio 6.0, but all the separate components are better integrated. All languages compile together to produce a single "package", which you then ship to your customers. There are no "installations" as the package is self contained. And it still includes a native C++ compiler which can still emit code for any Windows platform (except for .NET...)

      Microsoft says the combination of the above puts all languages on an equal footing: developers can code in whatever language suits them. (Since it's interpreted bytecodes, I think it makes all languages equally second class, but that's just me.) So with .NET language is not a barrier to function calls. You want to call method "Foo" on an object called "Bar"? You just do it in your working language, however that language invokes methods on objects. You don't know when you're writing it what language it will be called from. You don't worry when you're calling it what language it was written in.

      That's the developers' carrot in a nutshell. And so here's the developers' stick: Everything is shipped as bytecodes in that package, and the supplied decompiler already spits out source code that's only missing some of the documentation. I asked the guy during the .NET product introduction "How is intellectual property protected if anyone can just decompile the code?" The answer started out evasive, but boiled down to: We [Microsoft] will be serving up our meat-and-potatoes functionality via the web, so our code is hidden behind our firewall. Come, join us. You do not know the power of the dark side. (OK, so maybe the guy didn't say that last line, or at least not out loud.)

      On the whole, I was semi-impressed at the product introduction. Having strong type safety is really a good thing to me, because I do spend time fighting code that has been carelessly cast, and I also spend time converting from VARIANT arrays of UI1 to STD::strings. Automated garbage collection and automagic reference counting is also really nice. But interpreted languages haven't been exciting to me since GW-BASIC. (Sorry, you Java weenies, but I'm too old to think wasting cycles interpreting bytecodes in front of a user at run time is ever a good thing.) And C# is not C++, nor is it Java. I don't like that IL will only do its own random-time garbage collection and can not support destructors, not even virtual destructors. There are times when I want to garbage collect at a specific point in time (examples such as cleaning up scarce resources like database connections or sockets come easily to mind.)

      But I really, really don't like that .NET is ultimately just a facade to hide the movement of software to the subscription model under Palladium. Want to print that Word document? Did you tithe Microsoft this month? Nope? Too bad. Are you still offline? Too bad, you can't run PowerPoint.NET until you're back online and we can check the status of your subscription (or at least check the status of your Visa card authorization.) .NET will make Palladium viable, since the CLR is a trusted software container (read: sandbox.)

      So, on the whole, .NET has too many really huge negatives to get me going. It even caused me to ditch my MSDN subscription because it had become "Nothing but .NET" Literally.

      --
      John
    31. Re:This is hardly news... by Anonymous Coward · · Score: 0

      Let me see... how should the versioning work....

      NT-3.51 - First good stable NT...

      NT-4.0 - NT-3.51 with a good gui.... Should have been 3.52...

      Windows2000 - NT4 with another new gui... Yet another point release... Let's call it 3.53...

      XP - NT4 with yet another new gui... Again, a point release... nothing to see here... Let's call it 3.54...

      If Windows were debian I doubt if anything past 3.53 would have made it into the stable feed yet.

    32. Re:This is hardly news... by MonTemplar · · Score: 2

      Makes sense, although MS still hasn't got it right in practice. The last time I looked, "Works Suite 2003" was shipping with "Streets & Trips 2002".

      S&T hardly changes, so it boggles the mind how MS could miss the schedule for including S&T 2003 in the suite.


      'Err... ah... ignore the old software behind the curtain... FOR I AM THE GREAT AND MIGHTY.. err.. BILL, YES, THE GREAT AND MIGHTY BILL!!!'

      --
      -MT.
    33. Re:This is hardly news... by Peartree · · Score: 1

      .NET is a subscription based service. Instead of buying licenses for your servers and users, you lease licenses.

    34. Re:This is hardly news... by MonTemplar · · Score: 2

      Let me guess... you've never used or written software for Windows, have you?

      The code base of the NT side of the family has changed dramatically between NT 3.51 and XP, although thanks to the backwards compatibility of the Win32 API a lot of the changes aren't immediately apparent.

      --
      -MT.
    35. Re:This is hardly news... by MonTemplar · · Score: 2

      No, they couldn't possibly do that - if they did, they's be two version behind Sun's Solaris (9.0) and a whole three version behind Apple's MacOS (10.2) - can't be having that! :)

      --
      -MT.
    36. Re:This is hardly news... by Anonymous Coward · · Score: 0

      Didn't know there was bad news associated with Win2000. Sure, it was about a year late, but does anyone remember that? No, all people know is that 2000 works like a champ, and when it comes to the server room it will be preferred over XP for years to come. I for one am glad MS is returning to semi-meaningful version numbers.

    37. Re:This is hardly news... by Anonymous Coward · · Score: 0

      thank you, thank you, thank you! yours is the first comprehensible answer i have ever received to the question, "what the hell is .NET anyway?".

      thanks for providing the time to provide a well-written, detailed explanation.

    38. Re:This is hardly news... by MonTemplar · · Score: 2

      Actually, it was originally supposed to be release in 1998, but was repeatedly pushed back due to changing priorities being handed down from Bill, which in turn was influenced by changes in the marketplace (Internet, Java, XML). Also, a lot of stuff that was supposed to be part of Windows NT 5 ended up being dropped, due to problems getting the technology working properly - this was Microsoft's now-rarely-mentioned Cairo project, which envisaged what is now planned for Longhorn and beyond, back in the mid-90s. The Register has a write-up on the history of Cairo, and what became of it.

      --
      -MT.
    39. Re:This is hardly news... by Anonymous Coward · · Score: 2, Interesting

      If it takes that long to explain it, then it's not going to sell.

      You also don't address the *use* .NET was put to. It was used as a marketing gimmick, and to justify getting people locked in to the system to pay for new versions and upgrade their systems.

      What is the problem that .NET as you describe is supposed to fix? It's success cannot be measured until that happens (I suspect it's unofficial goal is to get people to spend loads more money).

      My interpretation is basically that they've gotten a new language, and they are changing all their other languages to be like it. IMHO, NOT a good idea. Why use perl.NET if the only difference between it and VB.NET is the way you for a "for" loop? I would've been better impressed if .NET was a new language to be used in the Windows system (basically, like a more integrated shell script, with bells on). VB.NET would not exist, but you would have VB *bindings* to .NET. In this case, you'd get interoperability between languages bu sing the .NET bindings as a mediator. You would not have to learn the perl/C++ API for interoperation, just the .NET interop API, and MS would produce a .NET API for both perl and C++. .NET as the system API would be used like POSIX is currently for perl and C++ (MS could, and IMO *should* implement 99.9% of the POSIX requirements in windows, then use that as their basis for .NET).

      Ta.

    40. Re:This is hardly news... by Jugalator · · Score: 3, Informative

      .NET the "language" is an intermediate language bytecode called IL (Intermediate Language). (...) .NET the framework also contains the system class, which exposes all of the available platform functionality.

      .NET is the platform and more like the "thinking". There's no ".NET, the language", since .NET is just a concept. There's no ".NET, the framework" either; its title is simply ".NET Framework".

      Microsoft describes what .NET is:

      ".NET is the Microsoft solution for XML Web services, the next generation of software that connects our world of information, devices, and people in a unified, personalized way. .NET technology enables the creation and use of XML-based applications, processes, and Web sites as services that share and combine information and functionality with each other by design, on any platform or smart device, to provide tailored solutions for organizations and individual people. .NET is a comprehensive family of products, built on industry and Internet standards, that provide for each aspect of developing (tools), managing (servers), using (building block services and smart clients) and experiencing (rich user experiences) XML Web services. .NET will become part of the Microsoft applications, tools, and servers you already use today--as well as new products that extend XML Web service capabilities to all of your business needs."

      There's nothing more to it than that, really -- .NET is Microsoft's platform that directly supports and allow creation of XML-based applications and web services. Also read this, it might clear things up.

      --
      Beware: In C++, your friends can see your privates!
    41. Re:This is hardly news... by draxil · · Score: 1

      Yeah but an x.x revision system is so confusing, far better to handle subrevsions the microsoft way!

      Windows 95 version a
      windows 95 version b
      windows 95 version c
      windows 98
      windows 98 second edition

      See thats far less confusing.. Especially if you want to find out say, if you can use usb, it's like umm 95 c. See, yeah that was simple..

    42. Re:This is hardly news... by SteveX · · Score: 2

      Well, there was never a marketing push for MFC either (or even Win32) but they're both prevalent. .NET is a framework. Everything else with the .NET tag is either a rebranding of something that existed before, or something written with the .NET framework but .NET itself is a framework, the CLR, and some languages.

      -Steve

    43. Re:This is hardly news... by IamTheRealMike · · Score: 2
      Yeah. Good post. One thing:

      .NET also fully supports exporting and importing these objects via SOAP.

      Actually .NET uses a series of extensions to SOAP called .NET Remoting which adds object export. Otherwise you're limited to flat APIs, despite the name SOAP does not allow object transport via a network. Embrace and extend... sigh

    44. Re:This is hardly news... by AKnightCowboy · · Score: 1
      The code base of the NT side of the family has changed dramatically between NT 3.51 and XP, although thanks to the backwards compatibility of the Win32 API a lot of the changes aren't immediately apparent.

      Yep, but now that is irrevelent. Microsoft has combined their code bases for home and business OS's into XP (or so they claim). The Windows95 track is dead, NT is dead. The hybrid OS that would serve both business server needs and home user gaming needs that was promised to us in MS timelines in 1993 is finally here with XP. Or so they say. Apparently not?

    45. Re:This is hardly news... by vbweenie · · Score: 1

      Quoth AC, above:

      Why use perl.NET if the only difference between it and VB.NET is the way you for a "for" loop?

      The answer, I think, is that that's not the only difference. C and C++ compile to the same assembly language, but are sufficiently different for there to be good reasons for wanting to code in the one rather than the other. I believe Perl's new VM, "Parrot", is intended to support bytecodes from other languages besides Perl.

      Microsoft's IL is not 100% generic - it's reputedly difficult to compile a language like Python to it sensibly, for reasons largely to do with typing if I understand aright - but it's generic enough to support multiple programming idioms that are different enough for programmers to have reasons to choose one over another, and those reasons will be the usual ones to do with familiarity, expressiveness, appropriateness to the problem domain, corporate politics and blind zealotry.

      For my purposes, as a coder already locked into the MS world in my day job, MS's redesign of their fundamental API for Windows programming is the strongest "draw" in .NET; that and the XML/SOAP support, which is integrated into the .NET languages and tools to an extent that is unprecedented in the MS world, and probably elsewhere too. Maybe JAXP comes close: I wouldn't know.

      It looks to me as if .NET comprises some of the best development work MS has done for ages - certainly some of the most ambitious. That doesn't mean it will, or should, rock your world if your world revolves around Java, or Perl, or Common Lisp or whatever. But for those of us who are already in that dismal place known as MS platform lock-in, it's a ray of light to say the least.

      --
      Experience is a hard school, but fools will learn no other.
    46. Re:This is hardly news... by vbweenie · · Score: 1

      Correction: C and C++ compiled with a compiler targetted at the same architecture compile to the same machine code.

      Then again, it's surely not impossible to come up with a C# compiler that compiles to something other than MS IL - Java bytecodes, for instance, or native machine code...

      --
      Experience is a hard school, but fools will learn no other.
    47. Re:This is hardly news... by MonTemplar · · Score: 2

      Yep, but now that is irrevelent. Microsoft has combined their code bases for home and business OS's into XP (or so they claim). The Windows95 track is dead, NT is dead. The hybrid OS that would serve both business server needs and home user gaming needs that was promised to us in MS timelines in 1993 is finally here with XP. Or so they say. Apparently not?

      You got that right! :)

      The problem is, although Windows 95/98 and Windows NT (as an add-in for NT 3.51, and integral in NT 4) share a similar UI, the Win32 API that each platform supported was markedly different. Windows 9x lacked the security APIs and (for a long time) OpenGL, whilst NT did not have the direct hardware access that Windows 9x could fall back on. Also, the hardware driver architechture was completely different between the two.

      This was one of the problems that caused the release of what would become Windows 2000 to be pushed back - the new Windows needed to support the features and idiocyncrasies of both platforms, in order to support the *applications* that were being used on either platform. This was the crucial part - it didn't matter how technically superior the new Windows was, if the customer's existing applications wouldn't run properly then it would sink, and quite possibly take Microsoft with it. (Remember, Windows 2000 was the *only* option at this point, there was no Plan B waiting in the wings).

      Some links for your further enlightenment :

      Microsoft Windows History
      Another potted history of Windows (warning - pop-ups lurking here!)
      The official word on the name-change to Windows 2000, from Microsoft PressPass
      An article on the historical links between Windows NT and VMS (They're more related than you think!)
      'Why Windows NT 5.0 Will Make the World a Better Place', written in September 1997(!) by Jesse Berst for ZDNet Anchordesk. Gives a run-down of the feature list at that time, and also gives a figure of how long NT 5.0 had been in development at that point.
      'New Windows could solve age-old puzzle', courtesy of News.com - a write-up of the (in)famous Cairo project, and where it fits into the Windows story.

      Food for thought, I thing you'll agree.

      --
      -MT.
    48. Re:This is hardly news... by plover · · Score: 2
      I'm sorry, but that quote from the Microsoft FAQ never cleared anything up for me. It's like saying "We have developed a motive device used to convey substances from a point to another point." They could be describing a car, a bucket, or a fish's stomach.

      Perhaps I divided it up in arbitrarily labeled fragments based on my understanding. But none of the Microsoft marketing drivel ever made anything clear. This is how I explained it to myself.

      --
      John
    49. Re:This is hardly news... by plover · · Score: 2
      You also don't address the *use* .NET was put to. It was used as a marketing gimmick, and to justify getting people locked in to the system to pay for new versions and upgrade their systems.

      I did mention at the very bottom that I think .NET is being used as the "Gateway to Palladium." I don't believe it was created to that end, but its architecture certainly lends itself to absolute OS control of the machine. And that's the ultimate lock-in.

      What is the problem that .NET as you describe is supposed to fix?

      I think the problems Microsoft is addressing are twofold: One, make development "easier" by improving type safety and allowing free choice of languages. Easier development leads to more development per developer, therefore developers are more "productive." Also, it should improve platform stability. (Carrots.) Two, it will help Microsoft make more money by moving end users to a subscription-based model of software sales. (Stick.) All of these help Microsoft, but only the stability portion helps the end user.

      My interpretation is basically that they've gotten a new language, and they are changing all their other languages to be like it.

      It's not really a new language, it's a mostly-familiar set of front-end languages (VB.NET ~= VB, C# ~= C++) to a new bytecode language, and a new API beneath it.

      New bindings in code to .NET beneath wouldn't solve the current DLL hell problems. And the old languages don't improve reliablity just because they're generating bytecode. The automatic memory allocation and deallocation means that there will be almost no chances for buffer overflows or memory leaks, the biggest contributers to crashing under Windows today. Sure, programs can still be written "wrong", (such as add $1.00 and $2.00 and come up with $2.99) but they won't be as likely to crash the platform beneath themselves or corrupt other unrelated applications.

      --
      John
    50. Re:This is hardly news... by plover · · Score: 2
      Hey, I'm locked into MS by my day job as well. But that doesn't mean I'm going to be seduced by the plusses offered. I see only the looming stick of Palladium at the other end of that path, and I fully intend to be running Linux or FreeBSD at home full time before that.

      I just need to have a distro I can convince my wife, son, brother-in-law, mother and sister to run. It's very hard to tell them "Hey, you can't buy software at Target or Best Buy any more because we run Linux now." That's not a big selling point.

      --
      John
    51. Re:This is hardly news... by DaytonCIM · · Score: 2

      I got that .NET was quite a bit more than .NET server. My point was simply that Micorsoft Marketing failed to promote .NET.

      In the past Micorsoft has always found a way to market it's products. However, they always marketed their products individually... Windows 9x to everyday end users and coding tools to industry users, for example.

      With .NET encompassing everything, I don't think MS could determine a good way to market it. In addition, I think someone realized that maybe all the time and money used to create such strong brand recognition would be for naught if they continued to try and change the "brand" to .NET.

      Of course, that's just my 2cents.

    52. Re:This is hardly news... by DaytonCIM · · Score: 2

      You nailed it: a rebranding. I think MS Marketing woke up and realized if they continued they would actually be trying to re-brand (thus competing with itself) products that already have the strongest brand in the business.

    53. Re:This is hardly news... by DaytonCIM · · Score: 2

      Like I said, last year: lots of interviews and press releases, some good technical articles and some small ad work and then the release of the manuals. The manuals had nice graphics and some new content.

      Then, soon after the push began, everything stopped. Then, the negative articles and rumors began to fly and the push just stopped.

    54. Re:This is hardly news... by JWSmythe · · Score: 2

      I need to hijack a friend's Win2k machine one of these days, so I can play with it. It still doesn't work under Linux. :(

      ---
      From their FAQ:
      ---

      1.1.2 What OSes are supported/not supported?
      The largest OS requirement for Terrarium is that the OS properly supports the .NET Framework. Please review the .NET Framework documentation and make sure your OS is supported by at least the redistributable package. The second OS requirement for Terrarium is that DirectX 7 is supported. The Terrarium graphics make use of DirectX 7 in order to achieve complex scenes with a minimum of CPU and Graphics processing time. Given the above requirements the following OSes are recommended by the Terrarium team for both running a client and for doing creature development.

      * Windows 2000, Any Flavor.
      * Windows XP, Home/Pro.

      The following OSes are not capable of running the Terrarium due to software constraints.

      * Windows NT 4.0

      The following OSes have not been heavily tested and may be used, but may have unknown issues or complications.

      * Windows 98
      * Windows ME
      * Windows .NET Server

      ---

      --
      Serious? Seriousness is well above my pay grade.
  2. Re:Big Fucking Whoop by Anonymous Coward · · Score: 0

    Do they call you the Customizer?

  3. Full of Holes... by akiy · · Score: 5, Funny

    A net, by defition, is full of holes...

    --

    --
    http://www.aikiweb.com - AikiWeb Aikido Information

    1. Re:Full of Holes... by Anonymous Coward · · Score: 3, Funny

      defition

      Yes, that's right. A net is where you put "de fish in".

    2. Re:Full of Holes... by msheppard · · Score: 3, Funny

      new name = Sieve Server 2003

      M@

      --
      Krispy Cream is people
    3. Re:Full of Holes... by jdreed1024 · · Score: 0, Offtopic

      What humorless wanker modded the parent as "Troll"? It's +1 Funny. Wish I had mod points...

      --
      There is no sig, there is only Zuul.
    4. Re:Full of Holes... by rbolkey · · Score: 3, Funny

      No, that's not the net they are talking about. The net they're talking about is short for network, which is something fishermen do with nets.

    5. Re:Full of Holes... by Anonymous Coward · · Score: 0

      Oh, come on Moderators. Have a sense of humour! That was hilarious!

    6. Re:Full of Holes... by Anonymous Coward · · Score: 0

      What's a "defition"?

    7. Re:Full of Holes... by Anonymous Coward · · Score: 0

      What's a "defition"?

      Pronounce it.... (duh-FISH-un). Like the other A/C said... a net is what yo' fishermen put da fish in. Also known as working with a net... or networking. ;-)

    8. Re:Full of Holes... by Trick · · Score: 4, Funny

      Well, yes, but a DOT net has very small ones.

    9. Re:Full of Holes... by skinfitz · · Score: 3, Funny

      Well, yes, but a DOT net has very small ones.

      Is that NetBIAS?

    10. Re:Full of Holes... by Bald+Wookie · · Score: 1

      No, but it's connected to a NetBEUI...

    11. Re:Full of Holes... by GrenDel+Fuego · · Score: 2

      The smaller the holes, the more you can fit in the same sized space.

    12. Re:Full of Holes... by Anonymous Coward · · Score: 0

      But it's good to know that Treebeard and friends have their own magazine these days.

    13. Re:Full of Holes... by Anonymous Coward · · Score: 0

      I wouldn't like it much if highways had holes, even if they are small...

    14. Re:Full of Holes... by darien · · Score: 2

      I had to read this about four times until I realised out why it's funny (which it actually is) - in England we pronounce "BEUI" as "b'yoo-wee" and "buoy" as "boy" ... our loss in this case, I guess. :)

  4. .NET? by Anonymous Coward · · Score: 0

    It's a trap!

    1. Re:.NET? by Anonymous Coward · · Score: 0

      Go back to Fark

    2. Re:.NET? by Anonymous Coward · · Score: 0

      LOL!

  5. Hmmm by hether · · Score: 0, Flamebait

    slapping .NET on so many Microsoft products has confused people as to what .NET actually means

    Crap?

    --

    Most people would die sooner than think; in fact, they do.
    1. Re:Hmmm by filth+grinder · · Score: 3, Funny

      When does Micro$oft plan to drop the $ from their name?

      oh wait...

  6. is it time? by smack_attack · · Score: 3, Funny

    Is it time to start callng it Microsoft bob.NET?

    1. Re:is it time? by Anonymous Coward · · Score: 0

      Was that supposed to be funny or are you just high on something?

    2. Re:is it time? by Anonymous Coward · · Score: 0

      maybe you are some 1998 script kid and don't know what MS bob is... eh?? dumbass.

    3. Re:is it time? by Anonymous Coward · · Score: 0

      No, I think it's that the original joke just wasn't funny, at all.

    4. Re:is it time? by Anonymous Coward · · Score: 0

      I'm a 1994 script kid. What is MS bob?

    5. Re:is it time? by Anonymous Coward · · Score: 0
      Dear Dumbass,

      I've been around for a long while and still found the original comment wildly unfunny. I did, however, find it convenient that you signed your post for my ease of response.

    6. Re:is it time? by Coke+in+a+Can · · Score: 1

      Hoo-hoo, that's good. I've gotta start using that myself.

  7. Ahahaha! by Anonymous Coward · · Score: 0

    .NET is great, too bad no one likes Palladium

  8. dotNet the .Net by stonebeat.org · · Score: 2

    and dotNet the Linux while you are at it.

  9. Confusion? by _ph1ux_ · · Score: 5, Insightful

    I agree with the bit about confusion....

    I was very confused (and still am) to exactly what .NET is - and palladium for that matter. I asked here on slashdot what they were and the major differnces between the two.

    Someone posted a link to an MS page that supposedly explained what they were - but it still was very vague and didnt help much.

    So - anyone out there clear on what .NET is and maybe palladium for that matter who would care to expound on the merits of this wonderful technology?

    1. Re:Confusion? by EnderWiggnz · · Score: 2, Informative

      in reality its a replacement for win32 api's .

      in marketing, its anything you want it to be.

      --
      ... hi bingo ...
    2. Re:Confusion? by Anonymous Coward · · Score: 1

      dotNet is Microsoft's attemp to wipe off Java.
      Paladium is Microsoft's attemp to make hardware unusable without a Microsoft operating system.

    3. Re:Confusion? by larien · · Score: 5, Informative
      .NET is their buzzword compliant strategy including SOAP, XML, Web services and their latest plan to crush competitors. Somewhere in there is the ditched Hailstorm/Passport plan for world domination.

      Palladium is the DRM, sorry, secure platform where the idea is that a Palladium enabled OS will only run signed apps, presumably adding security by not running any viruses, worms and any haxxor tools. Of course, this means any open source will not work in a Palladium OS because of the difficulty of getting an open source app signed.

      That's my understanding of the two, but I'm not 100% sure; it's been difficult trying to work out exactly what .NET really means...

    4. Re:Confusion? by jfroot · · Score: 2

      NET is their buzzword compliant strategy including SOAP, XML, Web services and their latest plan to crush competitors. Somewhere in there is the ditched Hailstorm/Passport plan for world domination.

      ok.. not to sound like a noob.. but what does THAT mean? I would like a specific example of how someone would use .NET in their everyday life.

    5. Re:Confusion? by Anonymous Coward · · Score: 0

      Of course, this means any open source will not work in a Palladium OS

      Not just open source, but just about any app that isn't from the "big guys" (or at least from someone willing to pay whatever fee Microsoft decides is suitable). It is a tool that practically guarantees a monopoly on the desktop.

    6. Re:Confusion? by Anonymous Coward · · Score: 0

      They are both the same in one respect, they are
      a method by which a convicted monopoly abuser,
      is again attempting to lock America (and the world) into another monopoly. .NET a unified language agnostic development framework that doesn't care what operating system you use as long as its windows.

      Palladium security brought to you by the most larcenous and incompetant software development firm on the planet.

      I'm so excited i'm getting tingly all over. :)

    7. Re:Confusion? by arkhan_jg · · Score: 5, Interesting
      .NET has already been answered fairly well.

      http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html is a good faq (in english, not geek ;)

      A sample ----

      2. What does TCPA / Palladium do, in ordinary English?

      It provides a computing platform on which you can't tamper with the applications, and where these applications can communicate securely with the vendor. The obvious application is digital rights management (DRM): Disney will be able to sell you DVDs that will decrypt and run on a Palladium platform, but which you won't be able to copy. The music industry will be able to sell you music downloads that you won't be able to swap. They will be able to sell you CDs that you'll only be able to play three times, or only on your birthday. All sorts of new marketing possibilities will open up.

      TCPA / Palladium will also make it much harder for you to run unlicensed software. Pirate software can be detected and deleted remotely. It will also make it easier for people to rent software rather than buying it; and if you stop paying the rent, then not only does the software stop working but so may the files it created. For years, Bill Gates has dreamed of finding a way to make the Chinese pay for software: Palladium could be the answer to his prayer.

      There are many other possibilities. Governments will be able to arrange things so that all Word documents created on civil servants' PCs are `born classified' and can't be leaked electronically to journalists. Auction sites might insist that you use trusted proxy software for bidding, so that you can't bid tactically at the auction. Cheating at computer games could be made more difficult.

      There is a downside too. There will be remote censorship: the mechanisms designed to delete pirated music under remote control may be used to delete documents that a court (or a software company) has decided are offensive - this could be anything from pornography to writings that criticise political leaders. Software companies can also make it harder for you to switch to their competitors' products; for example, Word could encrypt all your documents using keys that only Microsoft products have access to; this would mean that you could only read them using Microsoft products, not with any competing word processor.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    8. Re:Confusion? by Arethan · · Score: 5, Insightful

      Everyone is complaining that Palladium will kill open source on Win32. I can't help but agree, but there is another angle to this as well. What happens to the small programming shops? I can think of plenty of times when one of my previously employing companies wrote small (sometimes throwaway) apps for clients. Sometimes it was for data massaging, sometimes it was a quick front end to something normally complicated.

      The cold fact is that I can't see small businesses providing custom software solutions for clients surviving if Palladium is released. The cost to have throw away apps signed (not to mention the time delay involved) will utterly destroy them.

      Unless of course the application signing is much simpler than that. Simply trusting a company as a whole, rather than a particular application. Trusting an entire company will allow small businesses to sign their own code. Of course, that also means that the DRM is pointless because a single hacked network will result in signed viruses.

      If MS goes ahead with Palladium, I'll be keeping my eye out for the first virus to fool the OS into rejecting every app, regardless of signature. Perfect DOS attack. Can't do anything but reinstall from the installation media, if your DRM bios will let you that is...

    9. Re:Confusion? by nelsonal · · Score: 3, Interesting

      One of microsoft's test sites was a shipbuilder, the .Net features allowed the managers to setup MS Project schedules, and foremen could fire up their PocketPC handhelds and see what their teams were working on that day. Other examples would be allowing you to check on flight status with your cell phone or PDA.
      Its really just a buzzword laden branding strategy, that MS is using to try to convince people that web services, are all that and a bag of chips. Web services seem to be a fancy name for using xml to provide more useful data to end users of the data.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    10. Re:Confusion? by zero-g · · Score: 1, Informative

      You forgot one: Sloooow!

      Microsoft put on a demo of .Net at my school where they coded up this app then ran it on a laptop. When they got to the point where they ran the app, they decided to hand out raffle tickets. Needless to say, I was able to register a linux.com e-mail address long before the app started working. Funny thing is... they expect this to eventually work on cell phones and such. If it's slow on a decent laptop running wireless on top of an OC-3... well, you get the picture.

    11. Re:Confusion? by Anonymous Coward · · Score: 0

      If everything that is being said about Palladium by the actual engineers giving talks (and I highly doubt that they are lying - they are usually pretty respectable folks, unlike the people from the marketing department and the big bosses), then you are wrong. The way I understand it is that Palladium WILL give you a choice - do you want to run in the 'secure' (DRM, whatever) mode or not? If you choose no, then you might lose the ability ro run unsigned apps, yes. But you can always say yes, in which case you can run whatever you wish, but will lose the ability to play 'secure' content stuff.

    12. Re:Confusion? by Anonymous Coward · · Score: 5, Funny

      Is this all true? I was under the impression that .NET was a different four things:

      1. Developers

      2. Developers

      3. Developers

      4. Developers

      At least, that's what that Ballmer guy said.

    13. Re:Confusion? by thebigmacd · · Score: 1

      IANAexpert, but .net is a security and synchronization framework that applications can interface with to autoupdate for example. Different functions in the application can have separate methods of updating, and certain functions can only be accessed by users with specific rights. The original idea of Hailstorm was to provide web services where parts of the program would be stored locally, parts would run from a network drive, and parts would run from a web server. As well, hard disk storage can be abstracted to isolate programs from the rest of the computer. You can specifiy to which extent an application interacts with the operating system as a whole. Palladium is simply a hardware/software system for verifying and authorizing applications and data for use. An example of someone using .net is installing a program that can read and analyse any file on the computer, but through .net restrictions can only save to its allocated disk space fragment. as a matter of fact, when the program goes to save something, all it knows about is its home dir, but when it reads, it sees everything.

    14. Re:Confusion? by larien · · Score: 2
      Er, couldn't you check on flight status just as easily with a cookie-enabled web browser? Or some other client-server application?

      Seems like a lot of crap just to give client-server with XML to me...

    15. Re:Confusion? by Proc6 · · Score: 5, Informative

      I write C#.NET stuff almost every day. All .NET is is a framework. A collection of programming objects that let you build apps by fitting them together, and writing the glue, rather than re-inventing the wheel everytime. If you know what the Java classes are, or MFC, .NET is very similar. .NET objects can be accessed by writing command line apps, windows GUI apps, and ASP web-apps. It makes it very nice to be able to know the same language for all 3, at least to me. I liked Perl for CGI, but couldnt use it to make a GUI app very easily. VB was queer, but worked for GUI apps, but not very strong for complicated apps. .NET framework includes a bunch of objects for dealing with everything from I/O to Databases to XML and Webservices.

      --

      I'm Rick James with mod points biatch!

    16. Re:Confusion? by Daniel+Phillips · · Score: 1, Offtopic

      I liked Perl for CGI, but couldnt use it to make a GUI app very easily. VB was queer, but worked for GUI apps, but not very strong for complicated apps. .NET framework includes a bunch of objects for dealing with everything from I/O to Databases to XML and Webservices.

      It sounds like you want Python. No, really. It covers everything you mentioned with style, and with this compiler extension it's fast too.

      --
      Have you got your LWN subscription yet?
    17. Re:Confusion? by NetFu · · Score: 4, Insightful

      What was the app? I've been working with .NET development for about 6 months and everything I've used on every hardware from 400MHz Celeron's to 3GHz P4's has run very, very fast. And IMO, C# is incredibly easy to program simple stuff in -- reminds me of when I started programming on that Commodore PET in 1979-1980 (hmm, from PET to .NET? cool...)

      Also, what language was it in? ".NET" could be practically any language supported in Windows -- C, C++, C#, Java, Visual Basic, among others. Also, you know there's a separate .NET Embedded, right? Probably more tuned for a phone, I would think (not to mention that any program developed for a phone would have to be different in some way from the desktop version -- not a straight port).

      Anyway, I'd love to take a look at any .NET app that ran slowly -- it'd be a first for me to see that...

    18. Re:Confusion? by archen · · Score: 5, Insightful

      Those were my thoughts as well until I realized that microsoft is going to have major problems for one reason: scripting. Are they just going to say "No Scripting" on windows? I really don't see any practical way to ever "trust" a script of any sort. So I would imagine Microsoft will be putting "untrusted" applications in some sort of sandbox (and probably a disadvantage as some sort of penalty).

      Small time apps will always be there no matter what MS wants. What Microsoft will eventually find is that their lack of open / free development tools is going to be a continual drag on windows development. I couldn't even begin to name all the development tools / languages you can use on Linux. On windows there is only a handfull and most if it is controlled by MS and is far from cheap. All this "trusted computing" stuff is just going to make Linux development more appealing.

    19. Re:Confusion? by DickBreath · · Score: 1

      I was very confused (and still am) to exactly what .NET is - and palladium for that matter.

      Wow! Just look at the replies to this.

      While most of them are correct answers, so were the answers ofthe blind men who described an elephant.

      --

      I'll see your senator, and I'll raise you two judges.
    20. Re:Confusion? by xombo · · Score: 1

      It is to my understanding that palladium just lets you play signed media, but the processor has to support it, it to protect against piracy, so that things can't be ripped because they will be encrypted with a (fairly large) key. The processor has the key that will allow you to play the media, but only do certain things to it, like not copying it. But I think until VGA/DVI/Audio Out are encrypted too, it will always be insecure.

    21. Re:Confusion? by zero-g · · Score: 2, Informative

      It was this voice translator app they whipped up in Visual Studio .Net that used the Babelfish translator.

      Even with an embedded version of .Net, I have my doubts. Especially when it comes to efficient bandwidth usage. Online time on cell phones isn't exactly cheap.

    22. Re:Confusion? by JohnFluxx · · Score: 3, Insightful

      Also note that even if the OS allows unsigned apps etc, your unsigned app sure won't be allowed access to the data that you want to manipulate, since that will probably be in some signed database program.

    23. Re:Confusion? by plaxion · · Score: 1

      Hah! As I recall, one or two certificates were issued by Verisign to an individual that simply claimed to be a Microsoft employee.

      Yeah, I have real confidence in such a scheme. NOT!

    24. Re:Confusion? by esarjeant · · Score: 5, Informative

      TBPH, I think Microsoft is attempting to conquor the elusive remote object invocation problem.

      At first, it seemed like some version of RPC might solve this problem. And then a little bit later, developers were promised that CORBA was the future. Somewhere in there OSF/DCE made a lot of promises. And then Microsoft threw COM out there, and tried to spruce up some security issues with COM+...

      Eventually EJB took hold, and now we have yet another way to remotely invoke objects via SOAP.

      While things are looking up, I think most developers are fairly frustrated at this point. After grappling with IDL's and disparate RPC mechanisms, IUnknown and VisualBasic... I think unless there is a conserted effort by the industry to address remote object invocations (including a robust security model) then all of these attempts will continue to flounder.

      --

      Eric Sarjeant
      eric[@]sarjeant.com

    25. Re:Confusion? by Anonymous Coward · · Score: 0

      .NET is Microsoft's implementation of Web Services.

    26. Re:Confusion? by stephanruby · · Score: 2

      .Net is an umbrella brand for many of their brands. The brands under that umbrella are usually related to each other and they are usually related to web services, but they don't necessarily need to be. Brands aren't designed to make sense. They're designed to make money.

    27. Re:Confusion? by Anonymous Coward · · Score: 0

      Probably? That is just pure speculation 100%. Data is accessed frequently through means such as SQL, and I seriously doubt that apps will check this digital signing of who is sending them SQL requests.

    28. Re:Confusion? by gmulert · · Score: 1

      "Unfortunately, no one can be told what .NET is. You have to see it for yourself."

    29. Re:Confusion? by andrewski · · Score: 1

      How the fuck is checking with your browser going to sell MS more software? That's what they're after.

      XML can be really cool. If you just limit yourself to text and ASCII graphics. But with Microsoft, what's inside the XML? Nuggets of binary data. Some of these are unreadable. They might as well just leave the XML out.

    30. Re:Confusion? by Malcontent · · Score: 2

      " .NET should also facilitate the possibility of cross-platform applications."

      Wow a great string of "weasel words". A definate possibility of a probable maybe!. It depends on what IS is.

      Apparently working at MS makes one very adept at wordplay.

      --

      War is necrophilia.

    31. Re:Confusion? by Anonymous Coward · · Score: 0

      Take the BLUE pill!

    32. Re:Confusion? by mrkurt · · Score: 3, Insightful


      If .net is really about trying to solve the problem of remote object invocation, why do it in pretty much the same manner that Java does it-- with a language runtime that, as it turns out, will run only on Windows, which slaps another layer on top of COM and essentially abandons DCOM? Why not instead just extend Visual Studio 6 COM/DCOM and make it easier to use XML, SOAP, and other web services protocols to do remote method invocations? As it is, it seems like .net imposes a performance penalty on Windows machines-- applications are slow.


      The only answer I can come up with is that .net is about locking developers, and therefore enterprises, into Windows. I conclude that .net is about a specific technology, and other object technologies (RPC, CORBA, SOAP) are about standards. In a perfect world, standards win every time, but MS will always see its best interest in forking away from standards to uphold its market share. I have been a Visual Basic developer up to this point, and I appreciate having COM as an object model and bus. I have been giving other object platforms a serious look, though, as well as the open source tools associated with them, to see if it makes any sense to adopt one or the other.

      --
      Always look on the briight side of life! (whistle, whistle)
    33. Re:Confusion? by timeOday · · Score: 2

      For me, the big breakthrough was accepting that there is no real definition. Some things are definitely .net, some things are kind of related to .net. Think of words like 'liberal,' 'fair,' etc. Somebody can come up with a definition for .net, but it's likely to be inconsistent with some uses by other authoritative (MS advertising) sources.

    34. Re:Confusion? by NineNine · · Score: 3, Interesting

      Sounds like .Net = COM objects. If that's the case, why don't people just describe .NET this way?

    35. Re:Confusion? by Anonymous Coward · · Score: 0

      These lyin' MS shills should get the hell outta here. All .NET projects I've heard of have been reversed in the past 6 months.

    36. Re:Confusion? by Fembot · · Score: 2

      Its only gonna be 6 months or so before some norweigan kid breaks the encryption protecting the signing, and then another 3 years before he's aquitted

    37. Re:Confusion? by Anonymous Coward · · Score: 0

      I just won twenty bucks that you would have to answer this question and no matter what you said your post would get a five.

      Thanks Dan and go Wizards.

    38. Re:Confusion? by ConceptJunkie · · Score: 3, Interesting

      It provides a computing platform on which you can't tamper with the applications, and where these applications can communicate securely with the vendor.


      Sounds good so far...

      The obvious application is digital rights management (DRM):

      Which, of course, is only of value to the seller.


      Disney will be able to sell you DVDs that will decrypt and run on a Palladium platform, but which you won't be able to copy.


      Which means I have to buy new hardware to play the new media. This is consistent for a company that will only sell their old movies "for a limited time" to artificially and capriciously drive up demand.

      The music industry will be able to sell you music downloads that you won't be able to swap.


      Yeah, but I'll need a computer to play them. No listening in the car anymore... unless I buy more new, expensive, and needlessly complex hardware.

      They will be able to sell you CDs that you'll only be able
      to play three times, or only on your birthday.


      No they won't. I would never buy such a product. Of course, the analog hole still exists. I've got a video capture card that does great analog audio capture. I've used it to make nice digital copies of casette recording I made as a kid.

      All sorts of new marketing possibilities will open up.

      Especially given that companies will deceive, if not downright lie to you. All kinds of new ways to screw the consumer. Of course, all these new electronics gizmos you will _have_ to buy will be complicated to use and prone to malfunctions (at least as first, but always harder to use than their pre-DRM counterparts). You don't need a degree in UI design to play a Victrola, but how many people can use all the features of their stereos or DVD players these days? How much fun will people have when not understanding your hardware prevents you from playing your media? ("I bought this 3-use DVD from Disney (a subsudiary of Evilco) but I only watched the first 30 minutes three times, because my mother called, the power went out, one of the kids wet his pants, etc, etc. Now I can't finish it...")


      TCPA / Palladium will also make it much harder for you to run unlicensed software.


      So much for software development, one of my hobbies. So much for Open Source software. Oh you say I can become a licensed software provider? For a "nominal" annual fee? Whoopie! I'll pay for that! NOT!


      Pirate software can be detected and deleted remotely. It will also make it easier for people to rent software rather than buying it; and if you stop paying the rent, then not only does the software stop working but so may the files it created.


      So now companies can take over your computer and arbitrarily delete things. I'm sure that will _always_ work correctly and _never_ be misused, because everyone is completely competent and honest. We should always take every opportunity to give complete strangers control over us, because they know what's best.


      For years, Bill Gates has dreamed of finding a way to make the Chinese pay for software: Palladium could be the answer to his prayer.


      Not if they keep using Windows 2000 on existing hardware. Recall that these days the primary driving force for selling the latest and greatest hardware is 1.) Microsoft's (and others) increasingly bloated and inefficient software, and 2.) gaming. I use c. 400 MHz processors and don't feel like I'm missing out for 90% of what I do.


      There are many other possibilities. Governments will be able to arrange things so that all Word documents created on civil servants' PCs are `born classified' and can't be leaked electronically to journalists.


      Remember that joke about the dumb blonde photocopying her monitor to print out her document?


      Auction sites might insist that you use trusted proxy software for bidding, so that you can't bid tactically at the auction. Cheating at computer games could be made more difficult.


      And that will _never_ be compromised, because it's never happened in the past.


      There is a downside too.


      No, really?

      Sure, there will be some benefits, but as with everything in modern life, the trade-off will be much more complexity and hassle to do things that were formerly simple, and still more aspects of your life will be subject to being screwed up by the ineptness or malice of a complete stranger.

      Sign me up!

      --
      You are in a maze of twisty little passages, all alike.
    39. Re:Confusion? by shyster · · Score: 5, Insightful
      Mod the parent up. He's the first one with half a clue on what .NET is, rather than what MS is positioning on what .NET can do.

      Don't forget, however, that the .NET Framework also means that (theoretically, at least...and in reality for the most part) you can write in C#.NET, VB.NET, etc. and still have access to the same objects...so you can keep the language you're most familiar with.

      Also, .NET allows multiple versions of shared libraries, ending "DLL Hell" (which really hasn't been a problem for around 5 years, but whatever). It's also allows for granular and inheritable permissions on program's actions (Program X is allowed to access the network, therefore Component Y called by Program X is allowed to access the network)...though it requires a good development team that knows what they're doing and does it properly (so it probably won't work out too well).

      SOAP, XML, and Web Services are really just applications and languages of .NET...and a vision of MS's future program services (where your program can call on another program located on your server, or halfway around the world, to process data and return it...sort of like a global #include)...but it's not really living up to the hype yet.

      If you're not a developer or system admin, .NET means very little to you. If you're a developer, you probably should look into it, unless you're into Java. System Admins can probably wait a year or so before playing with Windows 2003 Server and some actual .NET applications.

    40. Re:Confusion? by shyster · · Score: 2
      I would guess that MS would put some code signing abilities into the domain controller's of the network, leaving the System Admin to sign code as safe. Therefore, the SA could sign scripts he writes, and sign custom apps as well as safe to run on member PC's.

      With Windows 2000 already including Certificate Services, I'd definitely put money on that road for program signing....Who knows what the hell it'll mean for digital media, though.

    41. Re:Confusion? by JohnFluxx · · Score: 2

      I appologise - I should have made it clear that indeed I was just speculating.
      You can quite easily see more and more programs keeping the data 'secure' by using palidum. Imagine your tax records program, your photo program, your databases. I can quite easily see MS-SQL defaulting to protecting your data. The only programs that can then gain access to the data are other signed programs. This would be flaunted as way to stop viruses modifying the data.

    42. Re:Confusion? by WasterDave · · Score: 2

      The cost to have throw away apps signed (not to mention the time delay involved) will utterly destroy them.

      Oh, do get a grip. You think monkey boy is going to jump around shouting "developers developers developers" then do a thing like that? MS know they need to keep the small development shops onside, and they're not about to crap on them. (Famous last words)

      I expect what we'll see is some arrangement where apps that run within the .net run time environment either don't need signing or have a light SSL'esque certificate attached. Code that runs natively, or more to the point can get to low level hardware will need approving by redmond though. So, a stock control application written in VB will have no problems, though a home cooked CD burner - or DRM cracker will have difficulty running.

      Dave

      --
      I write a blog now, you should be afraid.
    43. Re:Confusion? by nolife · · Score: 1

      foremen could fire up their PocketPC handhelds and see what their teams were working on that day.

      And they call that a good use of .net? Think about this situation for a minute. How the hell can a foreman really know or have a true idea how a major system overhaul is going by looking at a palm pilot? If he is satisified with recieving updates in that manner he should not be a foreman and should be working behind a desk in accounting adding up numbers or work for the planning department which is not involved with the actual work. I've worked in project management before in a shipyard environment. A PDA is great for standard messages, reminders, or reporting very specific tasks but that is far from what a foreman on down does.

      --
      Bad boys rape our young girls but Violet gives willingly.
    44. Re:Confusion? by Anonymous Coward · · Score: 0

      You are all fucking drunk since you're making stupid typos.

    45. Re:Confusion? by Kevinb · · Score: 1
      Of course, this means any open source will not work in a Palladium OS because of the difficulty of getting an open source app signed.

      I don't know how this meme got started, but it simply isn't true. Nothing in Palladium will stop an unsigned application from running unless the user explicitly requests it. From Microsoft's white paper on Palladium:

      A "Palladium"-enhanced computer must continue to run any existing applications and device drivers.

      "Palladium" is not a separate operating system. It is based on architectural enhancements to the Windows kernel and to computer hardware, including the CPU, peripherals and chipsets, to create a new trusted execution subsystem (see Figure 1).

      "Palladium" will not eliminate any features of Windows that users have come to rely on; everything that runs today will continue to run with "Palladium."

      Furthermore:

      "Palladium" is an opt-in system.

      "Palladium" is entirely an opt-in solution; systems will ship with the "Palladium" hardware and software features turned off. The user of the system can choose to simply stay with this default setting, leaving all "Palladium"-related capabilities (hardware and software) disabled.

      Bottom line: Palladium is going to be a Windows subsystem exposed through an API -- a feature, not a requirement. Apps can either use it or not use it if they choose, and users can either use it or not use it if they choose (and in fact it defaults to off).

    46. Re:Confusion? by tftp · · Score: 5, Insightful
      foremen could fire up their PocketPC handhelds and see what their teams were working on that day.

      I worked with architects and construction people, this should be close to shipbuilding. I *guarantee* that no foreman would even *think* of getting any usable info from a Palm Pilot. A foreman has heaps of A0 drawings (if you don't know what A0 size is, check it out), and most of those drawings are already in his head.

      A foreman does not *need* a computer. It is too slow, and has too low a resolution. Each drawing has tens of thousands pixels across, and we used all of those pixels - a building is long, and each room and each wall have their dimensions, and these dimensions must be readable.

      Also, a foreman does not need to check his Palm Pilot to know what his team is doing. That is because he is right there, with his team, running from one work site to another, checking the work and giving instructions all the time. That's what his job is about - not "checking his Palm Pilot".

      Frequently a foreman needs to talk to an engineer who oversees the construction. Then he reaches for his walkie-talkie, or walks to the office, usually with drawings in hand. Then he sits with the architect, who then draws sketches for him to explain this corner, or that insulation layer. A computer here is mostly useless, since pen and drafting paper are much faster. Pen is also easier to use, especially if a foreman does not have a university education.

      Computers are widely used as drafting tools, and they do this job reasonably well. But computer manipulation of drawings is not something that even an architect is good with. Most architects prefer pen and paper, and they all draw very well. Maintenance of the drawings is something that only draftsmen do.

    47. Re:Confusion? by Anonymous Coward · · Score: 1, Informative

      Sounds like .Net = COM objects. If that's the case, why don't people just describe .NET this way?

      The reason why people don't describe ".NET" as COM objects is because it encompasses so much more that just an object standard. I'm not sure, but I doubt there's too many hashtable com objects, or array list objects, etc... Most people would probably regard QIing & ref counting for these things too much. But ".NET" (really the part of .NET we're talking about w.r.t. COM is the CLR) offers that all and more. And it exposes all of it through COM (eg, ArrayList's CLSID is {6896B49D-7AFB-34DC-934E-5ADD38EEEE39}).

      On the other hand, COM and the CLR address the same problem and they are amazingly interoperable. They both are a means to offer reusable objects. But .NET adds to COM a whole bunch of metadata that allow neat things to happen. It adds garbage collection - no more ref counting, no more CoTaskMemAlloc. No more QIing. No more class factories. And it's designed to work across languages better than COM.

      And the reason why, despite all these cool changes, the two seem similar is that the CLR is
      the COM+ Runtime. That link discusses Visual Studio 7, COM+ 2.0 (including the COM+ Runtime), and Fusion 2.0 ("Solving DLL Hell"). Today we have VS.NET for VS7. We get fusion.dll w/ the .NET Framework. And we get the COM+ Runtime in the CLR.

      But to answer your question no one realizes it because of marketing :)

    48. Re:Confusion? by Fulcrum+of+Evil · · Score: 2

      if you don't know what A0

      For those who don't know, here's how it works (roughly). A4 is almost the same size as 8.5x11 (somewhat different and measured in mm). An A3 page is two A4 pages side by side. A2, 1, and 0 follow in the same way.

      when we get to A0 (which is really where the whole thing starts), we get a square meter of paper in the golden proportion (about 1.618 - I think it's (sqrt(5)+1)/2).

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    49. Re:Confusion? by Fulcrum+of+Evil · · Score: 2

      Imagine your tax records program, your photo program, your databases.

      So, when I get audited, I can't get at the return from 2 years ago because it was on a different computer with a different security signature. Sounds groovy.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    50. Re:Confusion? by Malcontent · · Score: 3, Interesting

      "Some .NET programs already run on other platforms - namely Mono enabled *nix."

      Yes trivial hello world ones and maybe other non gui apps which don't connect to a database. I guess that maybe somewhere around .001% of apps run on mono. I guess that means some to you. Mono is not even close being a mature product what is it's version number? .17. You point to a version .17 CLR and say that it runs some windows apps and expect me to take you seriously?

      ".NET runs in a virtual machine; its entire standard library is documentated, and it uses standardized plain text formats for communication. "

      Documented and open are different things.

      " Apparently working at MS makes one very adept at wordplay.

      You never quit do you? Are you this rude to all total strangers?

      1. Some .NET programs already run on other platforms - namely Mono enabled *nix.

      2. .NET runs in a virtual machine; its entire standard library is documentated, and it uses standardized plain text formats for communication.

      3. There are no technical barriers that are impossible to overcome which prevent .NET apps from running cross-platform.

      "4. The only barriers that exisit are in fact legal. We will have to see how they turn out."

      Given the past behaviour or MS I think we can take a fair guess at how this is going to turn out.

      "Satisified now? Or are you just going to continue to be an asshole?"

      I think I will continue to be an asshole as long as MS trolls like you get modded up so high here on slashdot.

      Listen cross platform languages are hard but they are not rocket science. Open source developers have written PERL, PHP, Python, Ruby, and a ton of other languages and toolkits that allow you to write cross platform applications. Of course somehow Sun managed to write java which does the same thing too.

      Either MS programmers are very very stupid and can't manage to write a cross platform CLR or MS does not want to. My guess is the latter.

      --

      War is necrophilia.

    51. Re:Confusion? by Arandir · · Score: 2

      Keystone is "Visual Studio .NET". Also the ".NET Runtime".

      And you say this is doing quite well? Hah!

      Visual Studio .NET is agonizingly slow. Click on a sidebar, and maybe it will slide open five seconds later. The only thing that keeps it somewhat useful is that the compiler, debugger, etc., are still traditional C/C++ binary applications.

      I've never used .NET Runtime, but talking with people who have, it's a nightmare in frustration. You have to clench your buttocks just right or you won't get a proper install. And then when you finally do, you have to make a saving throw on 3d6 to see if your previous applications still work.

      If .NET is the future of Windows, Linux, BSD and Solaris have nothing to worry about.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    52. Re:Confusion? by Loonacy · · Score: 1

      The main confusion behind .NET is the fact that services, applications, and libraries have the name.
      When you see Visual Studio .NET, C#.NET, VB.NET, etc., you think "Hey, .NET must be a development tool."
      Then you see Passport .NET, and think "No, .NET must be a service."
      Then you see Windows .NET and think ".NET must be a buzzword."

    53. Re:Confusion? by Anonymous Coward · · Score: 0
      1. Developers
      2. Developers
      3. Developers
      4. Developers

      Don't forget:
      5. Yee-Ha!
      6. Give it up for me!

      And of course:
      7. .Net
      8. ???
      9. Profit!
    54. Re:Confusion? by Kanasta · · Score: 2

      in theory developing for .NET has lots of potential

      but the problem is that they expect us to develop for it exclusively right now
      with the exception of VC.NET, you can no longer produce programs for Win32

      so if you want to produce Win32, you are forced to either use the outdated VS6, or use another company's tools. Now the problem is what happens when Microsoft flips a switch and only VS.NET programs will run on Windows.

    55. Re:Confusion? by IamTheRealMike · · Score: 2
      Anyway, I'd love to take a look at any .NET app that ran slowly -- it'd be a first for me to see that...

      Try implementing a 3D engine in C#. It won't have acceptable performance most likely. The speed of .NET apps is fine for desktop apps, because most desktop apps do not actually need high performance in the logic area, and because the vast majority of the code you use in such a project is not in fact .NET, it's inside the implementations of the .NET apis.

      Java is also quite fast when used in this way. See Eclipse for instance. They all have their uses. Note that .NET/C# has some abilities Java doesn't, like being able to temporarily turn off the garbage collector so allowing direct memory access which can improve speed quite a lot.

    56. Re:Confusion? by Sponge+Bath · · Score: 1
      At least, that's what that Ballmer guy said.

      A little off topic, but has anyone noticed how closely Balmer resembles (in behavior and appearance) the monster from the movie "Young Frankenstein"? .

    57. Re:Confusion? by nelsonal · · Score: 1

      Sorry, I only saw the video. I think it was more about schedualing and things of that nature, the foreman would be working in the rear torpedo room on the electrical system, and his welding team will be waiting for him before they are transfereed to Deck 2 and stuff, I don't think the blueprints were delivered to the forman via palmpilots.
      I don't think .net is supposed to deliver any new functionality (beyond java, xml, html, and scripting), than what other companies offer, it us just supposed to make it easier to impliment the functionality. I'm certianly no programmer, I can usually get a hello world out and that's about it, but in this case, I got to see a day on .net at an MS conference last winter.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    58. Re:Confusion? by Thaelon · · Score: 1

      Ok, I worked as a CAD operator (Structural Detailer was my job title) and I agree with most of what you say. A foreman isn't going to use a palmpilot to try and look at A0 size drawings. Also what is the point of of trying to flaunt your knowledge with cryptic "A0 size paper" why not just say "A0 (48" x 36" or the newer 44" x 34")"? But I disagree with you completely when you say:

      Computers are widely used as drafting tools, and they do this job reasonably well. But computer manipulation of drawings is not something that even an architect is good with. Most architects prefer pen and paper, and they all draw very well.

      Reasonably well? More like unbelievably well. An architect in this day and age that isn't good with computer maniuplation of drawings had better start learning or be left without a job. Tell me where these architects work that prefer pen and paper, I'll go steal their job. You can do infinitely more with a computer rather than pen and paper. Granted quick sketches for the forman will still be done on paper, but this is not the preferred method for full size drawings.

      --

      Question everything

    59. Re:Confusion? by Malcontent · · Score: 2

      " The guy asked for clarification and I gave a precise valid list! You provide nothing to the conversation! And who is the troll?"

      What you did was to post an advertisement for Microsoft. You played with words, you painted an overly optimistic picture, you told some of the truth but not the whole truth and certainly not "nothing but the truth".

      "But that doesn't mean that entirprising individuals won't come along and make it work without MS's help or approval."

      If those individuals are succesful they will be stopped by hook or by crook. That's what Bill Gates does. He destroys his competition using whatever means are his disposal (which are prodigious). Lying, cheating, stealing, intimidating, suing and so on just a matter of course at Microsoft. The reason for this of course is because Gates, Ballmer, Allchin, and the rest of the mafioso at the head of MS are all sleazy immoral bastards.

      " You continue to lie to people on here and pretend like you know I work for MS, even though on numerous occasions I have offered to provide you notarized proof to the contrary."

      Microsft is evil but they are not stupid. They are not going to hire astro turfers that work directly for them.

      --

      War is necrophilia.

    60. Re:Confusion? by multi+io · · Score: 1

      you can write in C#.NET, VB.NET, etc. and still have access to the same objects


      C#.NET and VB.NET (and managed C++) are more or less equivalent (the difference is only on the syntax level), and they were created to specifically meet the requirements of the CLR. This hardly proves anything.

      If .NET really is that language-neutral, then one should ask why MS created 1 1/2 new languages specifically for the CLR instead of porting, say, ANSI C++ oder VB6 to it.
    61. Re:Confusion? by Anonymous Coward · · Score: 0

      In terms of pure execution speed, .NET is even slower than Java. Which is not fast, but "fast enough".

      There's no significant speed difference between any managed .NET language. They all compile down to the same IL.

      My guess is that you are working with GUI applications, where most of the execution time is spent in native C++ libraries drawing widgets, and most of the rest is spent in DB connection time.

    62. Re:Confusion? by shyster · · Score: 3, Informative
      I'm not sure you understand here. The .NET Framework is a collection of objects (similar to the Win32 API's) that all .NET managed code has access to. Managed .NET code must be written with certain constraints, however.

      C++ is not designed with these constraints in mind. Managed C++ is, basically, C++ following those constraints (and is a mess). C# is a new language designed around those constraints, using similar syntax to C++ and Java (to make it easier to learn). VB.NET is a rewrite of Visual Basic that gives it a lot of the power of C++, but retains some of VB's simpler syntax (to make it easier to learn). They're not different only in syntax, though...there are differences in rules and functions as well. Sure, you can write programs that do the same things in VB.NET as in C#, but some things are easier in one than the other...which has pretty much always been the case with different programming languages.

      Standard C++ can be compiled with /clr and will be compiled to IL bytecode, therefore using CLR. You can not, however, use standard C++ to access the .NET Framework...that requires managed C++ (or another .NET safe language).

      But, C# and VB.NET aren't the only languages out there. ActiveState has Python.NET and Perl.NET, there's COBOL.NET, Fortran.NET, Forth.NET, and even Pascal.NET (and many others).

      But, managed code is a new addition to .NET that requires some adoptions in the programming languages. Why didn't MS port C++ or VB6 to .NET? They pretty much did...it's called Visual C++.NET and Visual Basic.NET.

      Like I said, if you're not a Windows developer (which you don't seem to be), then this largely means nothing to you.

    63. Re:Confusion? by Anonymous Coward · · Score: 0

      lol!

      its interesting to note that the monster had really big schlong

    64. Re:Confusion? by Anonymous Coward · · Score: 0

      I don't know anything about building construction, but I have spent a lot of time invarious shipyards.

      The construction/overhaul of a ship is a very complex process, with lots of teams working on different tasks in different spaces. Also the Navy puts immense pressure on contractors to track the status of all the projects, and uses this information to dole out the cash to the contractors.

      Properly implemented, allowing "management" to use computer projects to follow the daily chaos would improve their overall performance, however there is no whay that a Palm Pilot device could replace the need for drawings.

    65. Re:Confusion? by Anonymous Coward · · Score: 0

      .NET does somethings very quickly. For example, if your program is very memory intensive, it will tend to be quite slow. For kicks, I cloned a chess engine under .NET, Tom's Simple Chess Program, and ran it against the original. The original, written in C, ran about 20 times faster (by my rough benchmarks. With enough tweaking, I could probably drop that number to maybe 10x).

      For contrast, I do a lot of database work with .NET, and that's quick as a button. Mainly because I'm using only the objects that are part of the .NET framework. I can use C, C++, C#, VB, VB.NET, Java or even Cobol and still see the same performance because the bottleneck is my SQL server. Therefore, I go with ease of development, where .NET really shines.

      Critical thinking is very important. There is no one size fits all approach, use the right tool for the job, etc.

    66. Re:Confusion? by Anonymous Coward · · Score: 0

      I'm not sure you understand here. The .NET Framework is a collection of objects (similar to the Win32 API's) that all .NET managed code has access to.


      I know.


      Managed .NET code must be written with certain constraints, however.

      C++ is not designed with these constraints in mind.

      But, C# and VB.NET aren't the only languages out there. ActiveState has Python.NET and Perl.NET, there's COBOL.NET, Fortran.NET, Forth.NET, and even Pascal.NET (and many others).


      According to this article, Perl.NET wraps the normal Perl interpreter (running as unmanaged code) and lets Perl code access the .NET runtime via special modules ("use perlNET") and special comments in the source code. I'm not saying that this is not useful, but it certainly doesn't make Perl a fully integrated .NET language like C# or VB.NET. (I haven't looked at the other languages you mentioned)

      Jython, for example, has a better integration to the JVM (it's written in Java), and it does include a Python-to-Java bytecode compiler (though I don't know how well that one works).


      But, managed code is a new addition to .NET that requires some adoptions in the programming languages.


      The "some" depends. You should have a hard time integrating things like multiple inheritence, multiple dispatch, first-class functions or dynamic object systems (like Ruby's or CLOS's) into to the CLR as it stands today. AFAICS, you would either add these features yourself on top of the CLR (sacrificing a great deal of efficiency), or leave them out altogether, thereby making the language more similar to C# semantically.

      I'm not stating that .NET isn't useful. I merely object to the claim that now that we have .NET, we can potentially use any programming language we want without significant problems.
    67. Re:Confusion? by multi+io · · Score: 1

      I'm not sure you understand here. The .NET Framework is a collection of objects (similar to the Win32 API's) that all .NET managed code has access to.


      I know.


      Managed .NET code must be written with certain constraints, however.

      C++ is not designed with these constraints in mind.

      But, C# and VB.NET aren't the only languages out there. ActiveState has Python.NET and Perl.NET, there's COBOL.NET, Fortran.NET, Forth.NET, and even Pascal.NET (and many others).


      According to this article, Perl.NET wraps the normal Perl interpreter (running as unmanaged code) and lets Perl code access the .NET runtime via special modules ("use perlNET") and special comments in the source code. I'm not saying that this is not useful, but it certainly doesn't make Perl a fully integrated .NET language like C# or VB.NET. (I haven't looked at the other languages you mentioned)

      Jython, for example, has a better integration to the JVM (it's written in Java), and it does include a Python-to-Java bytecode compiler (though I don't know how well that one works).


      But, managed code is a new addition to .NET that requires some adoptions in the programming languages.


      The "some" depends. You should have a hard time integrating things like multiple inheritence, multiple dispatch, first-class functions or dynamic object systems (like Ruby's or CLOS's) into to the CLR as it stands today. AFAICS, you would either add these features yourself on top of the CLR (sacrificing a great deal of efficiency), or leave them out altogether, thereby making the language more similar to C# semantically.

      I'm not stating that .NET isn't useful. I merely object to the claim that now that we have .NET, we can potentially use any programming language we want without significant problems.
    68. Re:Confusion? by shyster · · Score: 2
      According to this [devx.com] article, Perl.NET wraps the normal Perl interpreter (running as unmanaged code) and lets Perl code access the .NET runtime via special modules ("use perlNET") and special comments in the source code. I'm not saying that this is not useful, but it certainly doesn't make Perl a fully integrated .NET language like C# or VB.NET. (I haven't looked at the other languages you mentioned)

      Okay, so it looks like Perl.NET hacked out of the CLR managed code bit, but others (I know Pascal.NET does, and I think Fortran.NET) can produce true managed code. Maybe it's beacuse Perl is an interpreted language?

      I merely object to the claim that now that we have .NET, we can potentially use any programming language we want without significant problems.

      Well, you indeed can write a block of code in Perl.NET, inherit it in C#, then override it. And you can use just about any language to get access to the .NET framework-even if you can't write true managed code with it, your developing life is still easier. If you use a real programming language, then your developing life is much easier. =)

    69. Re:Confusion? by tftp · · Score: 1
      cryptic "A0 size paper"

      There must be a bit of mystery everywhere :-) After all, this is hardly a trade secret. You rarely select such size for a printer (unless you just happen to have an HP plotter), but it's there, in the combo box.

      More like unbelievably well.

      Well, yes. It is somewhat easier to stretch a room a little in AutoCAD, instead of redoing the whole drawing. Hmm, looks like I did it again :-)

      Tell me where these architects work that prefer pen and paper, I'll go steal their job.

      They work in a big city in Minnesota that is more like two cities.

      You can do infinitely more with a computer rather than pen and paper.

      Yes and no. It depends on how much you personally must do, and how much help (CAD operators) you have. Pen in hand is quicker, if you only need to draw a small section here or view there. It all depends, of course. One person was personally attending to floor tiles, but another just took a highlighter and marked rooms according to the floor type. Then I had to put all these markers in all these rooms myself :-) In another case, an architect asked me to draw an elevation of a specific building (we had 46 of them, IIRC), and after that was done he used his favorite red pen to get rid of some stuff and to add some (stucco, as I recall). That was his style; other people had other styles of work.

    70. Re:Confusion? by tftp · · Score: 1
      Where I worked, they used MS Project to do the project tracking. It has little to do with actual construction work, though. A foreman would report the progress back to the office once a day, and that's it.

      The flaw in the original reasoning was that the foreman does not need external info to find out what his men are doing; he is the *source* of that information for everybody else. The foreman only needs a walkie-talkie to be happy. Besides, nobody is going to accept a click on some Palm Pilot device as a substitute for a complete set of paperwork.

    71. Re:Confusion? by Malcontent · · Score: 2

      You continue to troll for MS and I continue to troll for open source. The difference between you and me is that you troll for a corporation and I troll for an ideal.

      --

      War is necrophilia.

    72. Re:Confusion? by Malcontent · · Score: 2

      As I said before. What you posted was for all practical purposes and advertisement for MS. You did this is typical manner of PR agencies and AD agencies namely by presenting one side of the argument and a limited version of the truth. For example you used your "weasel words" (which most PR agencies do) to suggest that .NET was a cross platform strategy. You made similar comments about all the other .NET components. I called you on it and now you are upset. Too bad.

      "You troll not for anything positive but for destruction, interruption, and hate."

      I am simply trying to counteract an organized effort by the MS trolls on slashdot. All pro MS posts get moderated up to 5 due to your and your fellow MS astroturfers efforts. When a corporation organizes an attack like this on a community it's destructive.

      I don't hang out at gotdotnet or other pro MS sites and hype open source or java and you should not hang out here and hype MS.

      Destructive and hateful describe Microsoft not me. I didn't call you a communist, I did not call you a cancer, I did not refer to you as a virus, I did not try to paint you as a terrorist. If I had done any of that then maybe you could accuse me of being hateful.

      I also don't get paid by anybody to hype open source, nor do I make any sort of a profit from open source. I dont' sell any OSS products and I don't offer any OSS services. My "trolling" for open source is purely altruistic. Can you say the same about your trolling?

      --

      War is necrophilia.

    73. Re:Confusion? by Malcontent · · Score: 2

      " There was not one iota of "hype". Not one. You can't find. Opinion, yes (in that section). Fact, yes. Speculation, yes. No hype. No glorification. No unfounded joy. No adulation. You are making stuff up to suggest elsewise."

      I think that any rational human who read your post would conclude that it was indeed hype. If you think what I said qualifies as "horrific abuses of decency and ettiquitte" and then make a comparison to my posts in this thread with the criminal and sleazy actions of MS executives then that speaks for itself.

      As for the rest of your post I don't care what you think of me. You can ramble on all you want about

      --

      War is necrophilia.

  10. Oh no! by Anonymous Coward · · Score: 0

    Now Slashdot will have to change all those MS .Net advertisements they have. :(

    Hypocrisy at its greatest.

  11. Dot Net by Anonymous Coward · · Score: 4, Funny

    Bill: Nobody wants dotnet!
    MS Marketing : Let's rename it and fool the bastards
    Ballmer: * grin *

    1. Re:Dot Net by pi+radians · · Score: 2, Troll

      More like

      Bill: Nobody wants dotnet!
      MS Marketing : Let's rename it and fool the bastards
      Ballmer: * dances *

      --

      sin(6cos(r)+5A)
  12. forget the year numbers by stuuf · · Score: 1

    Just call it Windows NT Server 5.1.2600 like it probably is internally referred to by.

    --

    Everyone is born right-handed; only the greatest overcome it

    1. Re:forget the year numbers by Darth+Hubris · · Score: 1

      5.1.3668 was the last one I had a copy of, 'fore Siemens was booted from MS. I have RC1, and MS is inviting me to download RC2 now.

      --
      The party's over ... the drink ... and the luck ... ran out
  13. Microsoft forgets its failures quickly by Anonymous Coward · · Score: 2, Interesting

    With so much $ in the bank, they will let go of their failures quickly. Even though the tech community still teases them about Bob and crap like that, Microsoft pretend it never happened. Slowly, this will happen with .NET. It was a horrible idea from the start, and has severely backfired. Even though their credibility is ruined, they will move on and bumble around in the dark some more until they catch on to something. In the fable, the boy who cried wolf got three chances. Microsoft seems to get a lot more credit and trust from people than that, so it doesn't really matter that this has flopped on their face. They could have just released an upgrade to VB, but they had to sound like they had a lot more up their sleeves than that. They are casting a NET for a new strategy for the company, and they keep coming back with tin cans.

    1. Re:Microsoft forgets its failures quickly by Anonymous Coward · · Score: 0

      .NET is alive and well. This is simply a name change to one product. If you took your head out of your java ass you'd note that the .NET Framework is far more sophisticated than the Java classes and if you really look forward at what MS is doing to their apps, you'd see they're separating the OS from apps with .NET. Eventually, all of the MS apps will run on top of the .NET Framework and be portable to all OS's. Watch the Mono project this year. It's going to fuck with all the anti MS people because .NET will be cross-platform with your favorite open-source OS.

      Really, if you haven't looked into .NET and at least tried to understand the .NET framework (downloadable for free by the way), you're a moron. If you think it's going away, you're an even bigger moron.

  14. So does this mean .Mac can go back to iTools? by joel8x · · Score: 2

    Although iTools always sounded pretty lame, .Mac as a name never made any sense with the exception of its similarity to the name .Net.

    --
    Sound waves should be free!
    1. Re:So does this mean .Mac can go back to iTools? by Anonymous Coward · · Score: 0
      Nope. iTools would be difficult to switch back to. Besides the semantics (iTools was promised free for life, which apparently meant life of the service) there's the issue of other companies using the name (which was an issue before the switch, actually).


      Also, there is no .mac TLD as far as I know, so it's not as bad. .Net had the bad press from most Internet types of being the equivelent of a phone company releasing a new product consisting of a new calling plan called '1800' that didn't, as it were, necessarily or even commonly use 1-800 numbers...

  15. If only... by Sri+Lumpa · · Score: 2


    If only .Net could become a .Bob, maybe that would cut MS down a bit (didn't they say that .Net was a bet the company project?).

    --
    "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  16. Comment removed by account_deleted · · Score: 5, Informative

    Comment removed based on user account deletion

  17. Call it whatever you want by Anonymous Coward · · Score: 0

    It's still lightyears beyond the likes of linux and OSX.

  18. Surely a disapointment for ms? by posternutbaguk · · Score: 2, Interesting

    A name change may seem a small thing, but not too long ago microsoft were telling all and sundry that .NET would be the future of the computing world.

    The fact that they change the name to something NOT containing the magic term '.NET' must mean, at the least, that all the expensive PR has failed.

    microsoft need to actually demonstrate an actual use for .NET, after all, if I'm a qualified C++ programmer and I don't really know what it's 'about', how the hell is Joe Public gonna buy into this?

    1. Re:Surely a disapointment for ms? by Anonymous Coward · · Score: 0

      This doesn't change the fact that it is a yet another quality product from Microsoft which linux hippies everywhere are jealous of.

  19. maybe they should rename it to by Anonymous Coward · · Score: 0

    another classic microsoft "technology brand" that kinda meant a bunch of things:

    ActiveX

    It's active, and it's X .. hmm. ..

  20. This is News? by DAldredge · · Score: 0, Troll

    This is News?

    1. Re:This is News? by spells · · Score: 0, Troll

      No it's dotNews.

    2. Re:This is News? by Anonymous Coward · · Score: 0

      > This is News? (Score:2)
      > This is News?

      This is Redundant?
      This is Redundant?

  21. what I don't understand... by esarjeant · · Score: 2

    What I really don't understand is what MS hopes to accomplish by tweaking their product names only very slightly. So it use to be Windows 2000 Server and now it's going to be Windows Server 2003... big deal.

    If .NET was really a bet-the-business proposition, they might as well call the product what it is. Windows Server for .NET Version 1.0. Maybe MS has realized that .NET isn't as much a fundamental paradigm switch as it is a client/server application you run on your computer.

    And for that matter, the workstation version could be Windows Workstation for .NET Applications Version 1.0. That might actually help the consumer a little!

    Honestly, the users that were suppose to benefit from "consistent" naming conventions (Win 95, Win 98, Win 2000) have been duped with WinME, WinXP and whatever else MS is going to call their next workstation version of NT.

    Enough of these naming "conventions" already; call it what it is. IMHO, Apple is doing the most work in this area -- an OS is simply OS # - makes sense to me.

    --

    Eric Sarjeant
    eric[@]sarjeant.com

    1. Re:what I don't understand... by Proc6 · · Score: 3, Informative
      If .NET was really a bet-the-business proposition, they might as well call the product what it is.

      Which is exactly what they're doing. .NET Server was a misnomer, as it is strictly WindowsNT/2K code with the latest IIS and .NET Framework installed.

      A real .NET Windows will appear when the entire OS runs as managed code along with the rest of .NET. This next server OS is exactly what they've renamed it to, Windows 2003 Server.

      --

      I'm Rick James with mod points biatch!

    2. Re:what I don't understand... by Anonymous Coward · · Score: 0

      you should have gotten a 5 rating for those ideas

    3. Re:what I don't understand... by Habikki · · Score: 1

      I used to work for an ISP, and what I used to hate was when you would ask what Version of Windows they were using... I would normaly get "Internet Explorer" or "Netscape". Then what would annoy me even more was when someone thought that they were using 2000 becuase they had ME... or they were using ME and thought that they had XP. It just got really annoying after a while because you knew that you could fix their problem but it would take you 3 minutes to just find out what OS that they were using... bleh.

      It's not like many people know how to change the startup logo's for windows... and if they did they damn well would know what Version they had.

      Cheers,
      Robby

  22. great news by roalt · · Score: 2
    I just check whois and windowsserver200x.com is still available!

    I'm gonna be rich...

    1. Re:great news by Anonymous Coward · · Score: 0

      I just check whois and windowsserver200x.com is still available!

      or more likely, ..sued.

    2. Re:great news by Anonymous Coward · · Score: 0

      I just check whois and windowsserver200x.com is still available!

      I'm gonna be rich...


      or more likely, ..sued.

    3. Re:great news by shepd · · Score: 1

      >or more likely, ..sued.

      Twice? Isn't that covered by double jeopardy?

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
  23. heh by cetan · · Score: 2, Funny

    I bet a lot of domain name speculators/squatters are feeling good about their .NET-related purchases now...

    --
    In Soviet Russia...michael would be rotting in Siberia!
  24. aren't you being a little harsh? by Anonymous Coward · · Score: 0

    I'm sure .NET will catch up in a year or two, tops. :-)

  25. .net versus .WET by tenzig_112 · · Score: 2

    It's hardly surprising that they encountered market confusion considering how many people will always associate .net their internet provider's domain name.

    An even greater cause for brand confusion is the .wet initiative introduced at last year's Comdex show (which happened to coincide with a Vegas-area porn industry convention).

  26. Could this be yet another sign? by core+plexus · · Score: 2
    I'm wondering if we are seeing yet another sign of something shaking loose in Redmond? There's been all these unintended discharges of memos (Halloween, etc.), the deal with their faking 'switch' ads, etc. etc. And now this, appearing as if the left hand disagrees with the right hand. Anyone have info on a compilation of these and other 'slipups'?

    Personal Strap-On Aircraft for Auction on eBay

    1. Re:Could this be yet another sign? by smagruder · · Score: 2

      Prediction: Microsoft is the next Enron. You heard it here first.

      --
      Steve Magruder, Metro Foodist
    2. Re:Could this be yet another sign? by Anonymous Coward · · Score: 0
  27. Wired Article by bahwi · · Score: 3, Informative

    There's a blurb about it at the bottom of this Wired Article.

    One quote "Microsoft also is re-evaluating the ubiquitous name's use on other software." adds another dimension to this than just taking it off of the Windows 2003 Server.

  28. No no no.... by Dark+Lord+Seth · · Score: 2, Insightful

    It will be called "Microsoft Windows ($current_year + 1)" so that it won't LOOK terribly out of date for the next two years.

    1. Re:No no no.... by kliment · · Score: 3, Funny

      Nah, they can't do that, they'd be infringing on EA Sports' patented game naming scheme

  29. For a very detailed explanation... by NickSD · · Score: 4, Informative
  30. Anagram by Anonymous Coward · · Score: 0

    points out a similar article at ENT News

    Funny how a similar article's being posted to a news site that's an anagram of NET...

  31. a third choice by DeadPrez · · Score: 1

    Analysts are being quoted as saying that slapping .NET on so many Microsoft products has confused people as to what .NET actually means. Or could it be that customers know what it means, but nobody wants to buy it?"

    Actually its, "No one knows what .NET actually means nor do they want to buy it."

  32. The .NET stategy? I finally figured it out by hysterion · · Score: 1
    It goes as follows (note the Copernican inversion):

    Step 0: Profit!
    Step 1: ???
    Step 3: .NET

    Then we'll finally have enough .dots in the middle of all sentences that nobody knows where anything starts or ends.

    1. Re:The .NET stategy? I finally figured it out by Anonymous Coward · · Score: 0

      Wow, talk about a paradigm shift.
      They pretty much had us stumped all along...

  33. My theory... by hackwrench · · Score: 1

    My theory is that they couldn't get the .NET features that are supposed to be in the product done in time, so no (or not enough) .NET features no .NET designation.

    1. Re:My theory... by mattc58 · · Score: 2, Interesting

      Not so. They've actually frozen out on features for a while now. I'm a beta tester on the product--the new IIS 6.0 is nice.

    2. Re:My theory... by bergeron76 · · Score: 1

      My theory is that MSFT, (while faced with a more licensing conscious and ultimately wiser consumer market), tried a last ditch effort to create something worthwhile: .NET The problem, however, is that you can't sell the software utopia that is .NET . Sure it's a great idea on paper, and (expensive) marketing chimps can probably convince _anyone_ (even Billy) into thinking that it can be done. MSFT is realizing that they promised the world in a bottle with thier little .NET, and can't deliver. They're doing what any dog with it's tail between it's legs would do: Walking away.

      My prediction for 2003: Mid-to-end year they introduce another "Great technology that will revolutionize the world". Afterall, there's a sucker born every minute, and in the short term, they only stand to make a few billion off of people's stupidity. Ultimately it'll kick them in the ass, and people will start to realize that if you fool them once, shame on them, but if you fool them twice...

      --
      Don't think that a small group of dedicated individuals can't change the world. It's the only thing that ever has.
  34. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  35. All this proves by slycer9 · · Score: 2, Insightful

    is that M$oft knows the value of the public's perception. Other companies have pulled moves similar to this over the years, with far less fanfare (not to mention the griping and moaning).
    It doesn't matter what it's called people, all that matters is what it does.
    Mandrake, Suse, Slack...need I say more? Same thing (essentially) different name. .Net, WinSrv200X...doesn't matter, (assuming as based on the article) since all of the core is remaining the same.
    Name change only. As far as no one in the general public 'getting' what .Net was intended for...well, it wasn't intended for the GP now, was it?

    --
    Don't park drunk, accidents cause people.
    1. Re:All this proves by el_mex · · Score: 1

      Right on... Now if rms would realize that he's wasting everyone's energy and time by bitching about the silent "GNU" before "Linux"...

    2. Re:All this proves by Anonymous Coward · · Score: 0

      Mandrake, Suse, Slack...need I say more?

      Yes. Mandrake, Suse, Slack == Crap. Windows == Friendly. MAC OS X == More Friendly.

      Whats in a name? Everything.

  36. Instead it'll be Windows.museum by ink · · Score: 0, Offtopic

    No? Yes? Hopefully?

    --
    The wheel is turning, but the hamster is dead.
  37. Clarity is Good by InnovATIONS · · Score: 2
    Frankly the old name gave the impression that it was somehow specifically related to serving .net applications rather than being the next generation of the entire server platform (which it is)

    My guess is that the next thing that will nappen is that .NET Passport and .NET Services will get name and positioning changes, leaving .NET to be the one thing that it really was supposed to be in the first place, the common language runtime, framework, and development tools.

    I think that the reason why so many things got the .NET moniker was internal politics. For a while the mandate in Redmond was that the entire focus on the company was on internet development. So product managers, in the battle for upper management attention, and funding, decided that they had to somehow show that their product was part of the internet initiative and as part of that they slapped the .NET moniker to everyting.

  38. 'NET' means 'NO' in Russian by porky_pig_jr · · Score: 2

    so effectively it doesn't mean anything. No surprises Microsoft is backing out. THings would have been different if they're called this thingy .DA (YES)

    1. Re:'NET' means 'NO' in Russian by elemental23 · · Score: 2

      ITYM "nyet".

      --
      I like my women like my coffee... pale and bitter.
    2. Re:'NET' means 'NO' in Russian by Anonymous Coward · · Score: 0

      The actual spelling (in Cyrillic) is

      which can be transliterated as either "nyet" (which more accurately indicates pronunciation), or "net" (which has the same number of letters).

    3. Re:'NET' means 'NO' in Russian by Anonymous Coward · · Score: 0

      I'm reposting, because I forgot to preview the cyrillic characters.

      The actual spelling (in Cyrillic) is similar to
      HeT

      which can be transliterated as either "nyet" (which more accurately indicates pronunciation), or "net" (which has the same number of letters).

  39. What is .NET? by r · · Score: 5, Interesting
    i've been able to find at least three distinct meanings of the .NET tag:
    1. in the web development circles, it's used for next-generation tools and services for writing web applications. for example, ASP.NET, SOAP RPC, and various other web- and XML-based services

    2. in the web customer services domain, it was going to be a secure roaming account scheme, a.k.a. the Passport .NET

    3. most interestingly, in the windows application development domain, .NET is also used to describe the .NET Framework, a new set of libraries that's meant to slowly replace the standard Win32/64 libraries (see articles at ars technica for really detailed info). the framework is basically a cleaned-up, garbage-collected, language-agnostic version of Win32. it's great. but hardly anyone thinks about it when they hear .NET-this or .NET-that. :)

    in any case, the semantic shift of the label .NET has surely caused MS much grief. it's about time they cleaned it up.
    --

    My other car is a cons.

    1. Re:What is .NET? by harvardian · · Score: 3, Informative
      ASP.NET is "a compiled .NET Framework-based environment" (from gotdotnet.com) -- so basically it's a subset of the Framework with its own quirks like .aspx files that automatically compile. To illustrate this point, Response.Write() from ASP has turned into System.Web.HttpResponse.Write() in ASP.NET. So all of ASP.NET's functionality is in the global namespace, and ASP.NET can access the rest of the namespace hierarchy like any other program.

      Also, the entire .NET Framework is designed with XML-based services in mind, not just ASP.NET. Most (all?) classes can be serialized and passed around to be discovered by reflection.

  40. Not just because it was on every product. by fireboy1919 · · Score: 5, Insightful

    Rule #1 when creating technical terms is
    "Don't reuse a term that is already in use in a similar domain."

    This is pretty much exactly what Microsoft did. Putting a "." before a three letter word has become synonymous with meaning the webpage that displays the product. It is likely that some managers heard of visual studio .net and immediately checked "visualstudio.net" to find out what the name of the latest version of visual studio was.

    Plus, "net" is short for internet. That's nuts. We live in a world where a great many people don't know the difference between a webbrowser and an operating system. There's no way these people would be able to distinguish an internet api called "internet" from the internet.

    Its probably because they weren't really getting their corporate message across to consumers. I hear that the new API that they're building into all of their products is to be called "Owns You!"

    --
    Mod me down and I will become more powerful than you can possibly imagine!
    1. Re:Not just because it was on every product. by TimeTrip · · Score: 1

      Speaking of renaming a commoon word "net", after attending a microsoft codefest for .NET, they kept referring to "assemblies" as their name for the output of a project. Seriously, why did they choose the word ASSEMBLY? Especially since developers are the main users of the product!

      --

      You crazy man? You piss off supahfly!
    2. Re:Not just because it was on every product. by Anonymous Coward · · Score: 0

      I hear that the new API that they're building into all of their products is to be called "Owns You!"

      Don't be rediculous.
      *I* own you.

    3. Re:Not just because it was on every product. by serber · · Score: 1

      One could bring up a good point here: Windows .NET Server was not for consumers! It is a SERVER os.

      So that's just not really a good point is it...

      --
      Sometimes bad things happen.
  41. To bad... by mattyohe · · Score: 1

    microsoft wasn't name change happy back when they released "Microsoft Bob"

    --
    - what is the definition of simultanagnosia?! I've been meaning to look it up!
  42. Temporary setback by Anonymous Coward · · Score: 0

    Microsoft will overcome this temporary setback because most people like and use their products. They trust their vision for computing, and it looks like there are amazing things coming with Tablet PC, wrist watch computers (like Dick Tracy) and stuff like that. Everyone will want the devices to interoperate with Windows, and this strategy has worked extremely well for them thus far to have the switching costs far outweigh any incremental upgrade costs. They can afford to waste billions more on many failed strategies and not have to worry, since their marketshare isn't dropping at all, and maybe never has.

  43. In other News by certsoft · · Score: 2, Funny

    Ximian has announced that in response they will change the name of the "mono" project to "syphilis"

  44. just to make it more interesting by andih8u · · Score: 1

    They should really name the next server line Windows.OS2

    --


    slashdot, news for crazed liberal socialist zealots
  45. What .Net Means... by airrage · · Score: 2

    I think I remember reading an article that .NET was supposed to harken to, mentally, to a domain name extension. Such that .com is the extension for all commerical sites, .org for organization, so .net was going to be the "branded" starting point for all microsoft products. So I think they were trying to put all their products into some sort of directory tree. So .NET would be the root, and all languages would be .net, and the servers would be serverx.net, and products would be office.net, etc, etc. etc. However, where this really failed, for me anyway, is that .net is a misnomer, they should have created a new made-up extension. Secondly, I don't seriously think Microsoft had a good launch of this, they never could contain the marketing very well, you heard bits and pieces from all over the place, and never understood their direction from the top down.

    --
    "This isn't a study in computer science, its a study in human behavior"
  46. Why buy what's already free? by PseudoThink · · Score: 2, Informative

    The core of .NET is the .NET framework, which is somewhat analogous to the Java Virtual Machine. Both the framework and the .NET Framework SDK are free.

  47. . NET has nothing to do with it. by Ask-A-Nerd · · Score: 2, Insightful

    Your missing the whole point guys. They are trying desperately now to keep the name Windows. Why? Because of thier legal wrangling attempts to keep anyone else from using anything close like "Lindows". Not to mention .NET is another common used word that they would then be challenged on... why have two fights...just keep one. If they weren't using Windows anymore.. a judge might ask what the big deal was with someone else using something close. Get it?

    1. Re:. NET has nothing to do with it. by Anonymous Coward · · Score: 0

      That's a really brilliant point. It said in the article that they wanted to license the "brand" to different companies that are using it. Well, they're going to have a really hard time keeping that one, since so many websites and products use NET as part of their identification and have no relevance to MS.

  48. from what I understand by greechneb · · Score: 3, Funny

    .net means that when some clutz driving a forklift makes a mistake, the price of wine in china goes up?

    That's all I got from the commercial
    </sarcasm>

    1. Re:from what I understand by smagruder · · Score: 2

      Not only that, but you can also use .NET to almost, but magically avoid changing your new car color to Red before noticing the "no more sex" look on your girlfriend's face.

      --
      Steve Magruder, Metro Foodist
    2. Re:from what I understand by pediddle · · Score: 2

      Not only that, but you can magically paint the car *after* the windows and headlights have been installed. They must be using ForceField.NET.

  49. ActiveX by Iamthefallen · · Score: 3, Informative

    I've said it before, but I'll repeat myself, MS is run by lawyers and marketing people who don't consider any technical aspects of what they're doing. MS messed up bad with the ActiveX craze and maybe this influenced the move away from the .Net name. Very few still understand what .Net actually is, and MS isn't helping. I really wish they could have some of their techs/programmers sit down and write a coherent explanation/introduction, without lawyer/marketing influence. It took me a looong time to get a grip on it, simply because any MS material is so filled with buzzwords and marketing terms.

    For those that still don't know what .Net is, it's like an MS version of J2EE, not Java, J2EE. It's a architecture with among other things a large class library and a cross platform runtime that all .Net languages can run under.

    Ok, so it's not 100% accurate, but close enough.

    --
    Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
    1. Re:ActiveX by Anonymous Coward · · Score: 0

      It's not cross platform, until a version exists that runs the same on different platforms.

    2. Re:ActiveX by Iamthefallen · · Score: 1

      I believe the CLR already runs under BSD, Mono will bring .Net compatibility to Linux, and I'd be surprised if it's not also found on MacOS X soon.

      --
      Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
    3. Re:ActiveX by Anonymous Coward · · Score: 0

      Micro$oft-speak uses "cross-platform" to mean "runs on Win9x and WinNT" i.e. cross-platform WITHIN the MS family of Platforms.

      Wankers.

  50. Websphere by jasondlee · · Score: 0, Troll

    .Net is to Microsoft what Websphere is to IBM.

    jason

    --
    jason
    Have a good day?! Impossible! I'm at work!
  51. Much misunderstanding about .NET by Junks+Jerzey · · Score: 5, Informative

    I've seen a number of posts trying to clarify what .NET is, and they're missing the point. .NET isn't just about web services and so on, which in itself is a good reason to change the name. .NET is a major attempt to shed legacy Windows problems and modernize both Windows itself and Windows application development. If you read the .NET and C# documents, you'll see this. For example, if you want to write a GUI application for Windows today, you have to use one of (a) raw Win32 API, (b) MFC, (c) a cross-platform toolkit like WxWindows, or (d) a tool like Delphi or Visual Basic. By a large margin, the last of these is the cleanest and least stressful--if you're only concerned about Windows that is (of course you can get Delphi for Linux in the guise of Kylix). But .NET is bringing the GUI building features of Delphi and Visual Basic to the OS, so there's support for this from the ground up. Ditto for technologies like DirectX 9. No more do you have to deal with arcane C++ interfaces to COM, you can use a pretty little C# component.

    In short, Microsoft is deprecating most of the Win32 API, making .NET the preferred method for developing Windows applications. If don't like C#, that's okay. Microsoft has been getting indepdendent language developers to port their own languages to .NET, including lesser used languages like Smalltalk, APL, and Mercury.

    As much as I hate to say it, .NET could be a huge win. No more struggling with Petzold books, just use the much simpler .NET components. No need to hang onto awful legacy frameworks like MFC, which even Microsoft employees hate. No more having to choose between C++ and much slower scripting languages like Python for application development, just use C#.

    1. Re:Much misunderstanding about .NET by Anonymous Coward · · Score: 0

      It could be a huge win for MS, which almost by definition now, is a huge loss for everyone else. Microsoft's biggest problem is convincing people to base their business on any Microsoft-specific technologies. There are certainly companies that will be able to have a nice little niche business writing shareware or something like that for NET, but Microsoft will prey on any company that does anything really cool with .NET. So, if you want either to get purchased by Microsoft or go out of business eventually, then choose their technologies. Most people will continue to use their products, but the big problem is generating an INDUSTRY around any of them, like there is with Java and Linux. The problem for them, is that in order to grow at the rate they need to, they need to have industries around their technologies, not just use them in house. So far, .NET is an in-house tool that will make their employees more efficient.

    2. Re:Much misunderstanding about .NET by farnsworth · · Score: 2
      You made some good points but you glazed over an important detail: languages must support some basic features to implement the .net framework, and adding these features in to languages fundamentally changes that language.

      Even microsoft could not get their vb compiler to be backwards compatable with old code. if you have vb 6 code, you're stuck with it.

      The fact that COM can bridge all the languages that don't have the same basic object model is sort of genius in a sick way, but as it turns out, no one really cares about that.

      --

      There aint no pancake so thin it doesn't have two sides.

    3. Re:Much misunderstanding about .NET by Herkum01 · · Score: 4, Funny

      NET is a major attempt to shed legacy Windows

      HEY that is Linux's strategy! They cannot come with ANYTHING on their own anymore!

    4. Re:Much misunderstanding about .NET by big_groo · · Score: 2

      Pardon the ignorance, but what exactly is/are the differences between C# and C++ ?

      Is C# meant to replace C++?

    5. Re:Much misunderstanding about .NET by MeanMF · · Score: 3, Insightful

      Pardon the ignorance, but what exactly is/are the differences between C# and C++ ? Is C# meant to replace C++?

      Just think of it as MSJava without the trademark infringement. C# is actually more of a threat to replace VB than C++, since C# and VB are both run completely inside the .NET runtime and have just about the same features. C++ is still the language of choice for lower-level programming such as system utilities and device drivers. C++ offers a lot more flexibility to the programmer at the expense of additional complexity.

    6. Re:Much misunderstanding about .NET by mrkurt · · Score: 2

      In a sense, yes, C# is meant to replace C++ on Windows. C# is a new-from-the-ground-up programming language that is object-oriented. With C# on the .net platform, you can only write what is known as managed code, meaning it utilizes classes from the .net framework to build applications. Visual C++ is still available on the .net platform as well, and provides you with the ability to write both managed and unmanaged code-- where you don't use the .net framework and can instead write Microsoft Foundation Classes applications-- essentially, just like you can with VC++ 6.

      I don't develop with VC++, but it seems to me that using the .net version of the language to develop managed code would be very different from writing MFC apps-- the APIs are completely different. And, of course, both bear little resemblance to standard C++ or other development platforms. C# and the .net framework are a lot closer to Java in syntax than VC++ MFC, as well. So if you currently program with VC++ 6, and want to use managed code, you might have to retrain like the rest of us who were using Visual Studio 6.

      Any campers out there, correct me if my observations are off.

      --
      Always look on the briight side of life! (whistle, whistle)
    7. Re:Much misunderstanding about .NET by Anonymous Coward · · Score: 0

      "As much as I hate to say it, .NET could be a huge win. No more struggling with Petzold books, just use the much simpler .NET components. No need to hang onto awful legacy frameworks like MFC, which even Microsoft employees hate. No more having to choose between C++ and much slower scripting languages like Python for application development, just use C#"

      Thank you MS for getting rid of all those pesky choices. After all there was no need for all that choice in the first place, right? Looks like programming utopia is on its way (NOT)

    8. Re:Much misunderstanding about .NET by Anonymous Coward · · Score: 0

      The fact that COM can bridge all the languages that don't have the same basic object model is sort of genius in a sick way, but as it turns out, no one really cares about that.

      Actually, everyone on Windows cares about it, and that's why the unix guys have made 3 or 4 clones of it.

      There wasn't anything fundementally wrong with COM except for the BS object registration, that VB was a poor OO language, and that they couldn't sell a Windows-only technology into the enterprise market.

      But, MS envied the success of Java and decided they had to throw out the baby with the bathwater and legacy millions of lines of their and their customer's code.

    9. Re:Much misunderstanding about .NET by Anonymous Coward · · Score: 0

      Sorry, but Python is about a thin a layer on top of STL as you can get. I wanna see some real beanchmarks on this, as I bet Python is 2x faster than C#.

      Ruby is a much better core language tho it still very early and needs many more libs.

      Personally, I often choose s-lang to embed in my C apps, small fast, easy.

      JoeR

    10. Re:Much misunderstanding about .NET by bnenning · · Score: 2
      C# is a new-from-the-ground-up programming language


      Not exactly.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    11. Re:Much misunderstanding about .NET by Anonymous Coward · · Score: 0
      I'm no expert, so please correct me if I'm wrong. When I looked at the GUI API in VS.NET C#, the gui API still isn't nearly as complete as C++. Obviously someone can still reference the older MFC dll's, but from the current API that is available in VS.NET C#, it is not a complete function replication of C++ windows GUI API.

      I'm no expert in windows C++ API, so I could be totally wrong. One thing with C# is the reliance on schema, which sucks nuts. Schema is lame and doesn't support like referencing external classes as base classes w/o breaking compliance. Most of the schema drivers I've used or played with don't support the ability to pass a schema that references another object as the parent. It supports it internally, but not externally. I believe the Schema group is working on the next version to address these issues, but it is one of the biggest issues many developers have with schema. Obviously that breaks/goes against the intended use of Schema which tends to be used for RPC purposes. But that's like saying all RPC calls are only going to use self-contained objects that don't inherit from some other object structure.

    12. Re:Much misunderstanding about .NET by watzinaneihm · · Score: 1

      I was getting into it, then you have confused me again. I would use C when I wanted something that involved system level stuff, use fortran when I used arrays etc. I dont choose languages based on how easy it is to code etc. except in the case of python. Now if fortran.NET is as slow as python.NET why would I choose fortran.NET ?
      Also what are they going to do about languages like prolog and lisp which are altogether different in the way they work?

      I agree with the poster in saying that MS is ditching Win32 API . In this way they could make windows machine independant. ie after a few years release an OS which does not run byte code at all and call it " Win2007 home edition " . You want to run it, you run it on the VM. For real work you use the server edition which will let you run bytecode.
      The plus side is that hardware prices might come down due to competition. ie now if powerPC chip actually runs faster than Intel, users wont switch because thay cant run windows. It takes a long time for users to switch OSes by which time intel has a faster version out and user has no reason to switch. If we all ran on .NET VM or any other VM the PowerPC/Intel fight might actually be similar to todays Intel/AMD fight ( opteron and itanium run win32 code on emulation). Also remember that the framwork is open so it is possible that the software prices might comedown too.

      --
      .ACMD setaloiv siht gnidaeR
    13. Re:Much misunderstanding about .NET by Anonymous Coward · · Score: 0

      You missed the point C# and the CLR (which .Net basically is) is nothing short of a Smalltalk/Java with the removal of cross platform features. Basically this thing has been there for computer ages, but now that Microsoft has spilled it out it is brand new innovative, the greatest yadayadayada....

    14. Re:Much misunderstanding about .NET by Junks+Jerzey · · Score: 2

      I was getting into it, then you have confused me again. I would use C when I wanted something that involved system level stuff, use fortran when I used arrays etc. I dont choose languages based on how easy it is to code etc. except in the case of python. Now if fortran.NET is as slow as python.NET why would I choose fortran.NET?

      Python is, simply by its language defnition, going to be much slower than Fortran no matter what the platform. I *suspect* that Python.NET is just a quickie port to show that it's possible, not to amaze the natives with raw speed.

      Other more traditional languages, like FORTRAN, will still be slower in their .NET versions. This is simply because .NET provides more up front, like garbage collection. You get the same kind of overhead with any other heavier weight language, like ML and Lisp.

  52. What .NET is? Why not .NORMAL? by Scalli0n · · Score: 1

    My question is, how did M$ think that by changing the name of their services to xyz.NET were they gonna get me to buy them? I mean, I use windows and word and all that, but unless they give me concrete features, I dont think I'll buy.

    AND

    About .NET Framework; nobody ever knew what it was. I use PHP/MySQL and Apache/Linux; .NET purpoted to change my life, give me wings, and help me have children, but in the last 4 years, I still haven't seen a change in Jack Skizet.

    AND

    If that weren't bad enough, they went around mixing crap up;
    Passport (normal, dumb users) with
    Framework (developers, highly intelligent, cream of the crop, smartest, biased...) with
    XML (something that managers consider the next best thing to sliced bread).

    To business executives everywhere:
    DO NOT ever make normal people learn what programmers do! It frightens and confuses them! Normal people don't need to be scarred like that!

    Anyway, [/rant].

    --
    Sig & Below
    Yuck Fou
  53. Normal Microsoft by Anonymous Coward · · Score: 0

    This is just normal Microsoft operating procedure.

    We are Microsoft. Lower your firewalls and
    surrender your code. We will embrace and extend until we incorporate your technology into our own. Resistance is futile.

  54. Re:in soviet russia by nelsonal · · Score: 1, Offtopic

    The ISR jokes were as far as I know originated by a Russian comidian named Yakov Smirnoff, who used them during his peak popularity in the 1980s. He is now in Branson MO. His web page appears to be down, so here is a basic bio page on him.
    More recently, I think it was on an episode of "The Family Guy" that featured a Russian made car that spouted off ISR one liners. I am not sure of the exact show, but I asked the question earlier and got those two respones.

    --
    Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
  55. Slashdot Lemming Says by SlashdotLemming · · Score: 1

    I never could figure out what .NET was. Could someone please explain it to me?

    1. Re:Slashdot Lemming Says by Anonymous Coward · · Score: 0
      haha

      Not funny, troll.

  56. first impressions by zogger · · Score: 2

    tell ya whut my first impression when I heard the term "net" associated with "microsoft". OH NO YOU DON'T! They are RICH ENOUGH now, they made "enough" money as far as I am concerned, and they got a confirmed track record of the high level management there being lying weasels. I think of them the same way I think of professional sports "gods" and "artists" out of hollyweird, just way over-paid and over-valued and over-hyped for what ya get. And luckily I'm not in some "business" area where I am forced to use their stuff by the PHBs in order to "make money", thank goodness. I am not gonna get trapped in that "net"! Once is enough thankew very much!Just too many viruses associated with their products, too many security vulnerabilites, and for them to start throwing around buzzwords like "net" and "trusted" they can byte me. Paying 100 clams to get guaranteed viruses is not an option any longer, and any "businesses" still sucked into their crap are being run by idjits, they are wasting money time and effort by the truckload. It's no wonder the US economy is in such weird straights. How many clues do ya need?

    If I was car shopping, and I looked up and down the street and all I saw was "belchfire motors" cars in peoples driveways, and every hood was up and the car was being worked on every weekend, I would just not buy a belchfire, even if "everyone buys them" was the reality at the time. Enough's enough for that company, time to move on. When belchfire was first made, sure, it was cool, worked well enough, helped everyone get a car on the road, but something happened, and quality and security became "job 7896" for them. Time to let em go. The guys in the trenches can work someplace else, the fatcats there can live on the profits they got, and if that ain't enough tough kitty, that's the belchfire solution. The "stock holders" I could care less about, I don't believe in either usury or getting something for nothing in the wall street rigged casino scams.

  57. Ouch by SomeOtherGuy · · Score: 2

    I guess the new version of "Linux Server .ORG" is going to have to change it's name soon. And "Apple OS X .COM" will have to go south. "FreeBSD Server .EDU" may not get off scott free either.

    --
    (+1 Funny) only if I laugh out loud.
    1. Re:Ouch by DA-MAN · · Score: 2

      In keeping with Microsoft's naming conventions, shouldn't it be

      "Linux.ORG Server"
      "Apple.COM OS X Server"
      "FreeBSD.EDU Server"
      "Microsoft.NET Server"

      See the difference!

      Hehe, just nitpicking, sorry. You still a funny mofucka!

      --
      Can I get an eye poke?
      Dog House Forum
  58. Win XP has something to do with it by avandesande · · Score: 3, Interesting

    One thing that really differentiated the difference between .net applications and win32 ones was their appearance, which is different much like the way java apps look different. When Win XP came along with all the skins, this difference has evaporated. WinXP and .net apps have definitly taken some hints from kde/gnome world.

    --
    love is just extroverted narcissism
  59. Predicted in the Kuro5hin interview with Adam Barr by Milo77 · · Score: 1

    Q:Microsoft made a lot of noise about .Net and Hailstorm, but that seems to have died off now. Any idea what is going on?

    A:For whatever reason, Microsoft was for a period of time obsessed with the notion of subscribers, whether for software, or Internet access, or whatever, but the idea of people paying an ongoing monthly fee rather than buying packaged software when they wanted to. Now they do have some subscription plans going, with MSN and Xbox Live. But with .Net, they tried to put the cart before the horse in two ways, first pushing Hailstorm instead of .Net, and then talking up the subscription features of Hailstorm. This made the company seem greedy and also confused developers who were trying to figure out what .Net actually was. I think .Net could still be a useful platform for web services. But Microsoft has blown the explanation of .Net so completely that it may have to drop the whole thing, rename it, and start over. (emphasis mine)

  60. This means dead for the .net platform ! by Anonymous Coward · · Score: 0

    Just because the justice setlement just force MS to put Java on their windows if they want to put .net :o)

    MS has trap itself !

    Instead of creating a doomed platformed they should have stayed in the Java wisdom where they were the kind leader in the 1998's ! This is where politics tricks ;)

    Anyway, i've told a year ago that .net was the worst thing MS have ever done, but i did never imagine it could prove i was right so earlier !!!

    -JB'.

    1. Re:This means dead for the .net platform ! by Anonymous Coward · · Score: 0

      All your base are belong to us.

  61. Slashdot Lemming Says by SlashdotLemming · · Score: 1

    .NET??
    Should be called .NOT

    haha

  62. Passport dead? by jlleblanc · · Score: 1

    I still see Passport (with the .NET brand name) around. Try Expedia.com and scroll to the bottom of the login page. I remember hearing some story about Passport perhaps being less intrusive, but it does not appear to be dead.

    1. Re:Passport dead? by Tim+C · · Score: 3, Informative

      Passport still exists, but I think that take up has been much slower than MS wanted (ie virtually nonexistant). In fact, to order evaluation copies of Windows XP Professional and Office XP, I had to sign up for a Passport. To sign on to Hotmail (in IE 6 only?) or MSN Messenger, at least, you have to associate a Passport account with your XP user account, so no, Passport is not exactly dead.

      .NET My Services, formerly Halistorm, is (currently) dead. The computing industry and target clients essentially told MS where to shove it.

    2. Re:Passport dead? by TJamieson · · Score: 1

      To sign on to Hotmail (in IE 6 only?) or MSN Messenger, at least, you have to associate a Passport account with your XP user account

      Not true - when a user account is first logged into XP, it pops up a cutesy little message - something like "Add your Passport account to XP!" You can dismiss that warning, and Passport stuff will still work fine. For the record, IE6 on XP right now, and I can get to Hotmail just fine.

      --
      For the last time, PIN Number and ATM Machine are redundancies!
    3. Re:Passport dead? by aliebrah · · Score: 2

      To sign on to Hotmail (in IE 6 only?) or MSN Messenger, at least, you have to associate a Passport account with your XP user account

      This is completely incorrect. There is an option to associate your passport account with your XP user account, and this makes things easier sometimes. BUT, it is an option, you do not have to associate your passport account to your XP user account to do anything. In fact, most of my family at home uses both MSN/Hotmail together and separately on Windows XP without linking to their XP user accounts.

    4. Re:Passport dead? by Fulcrum+of+Evil · · Score: 2

      you do not have to associate your passport account to your XP user account to do anything.

      You may remember that, shortly after XP came out, there was a big stink because, while not requiring passport, XP's behavior strongly suggested (especially to the computer illiterate) that it was in fact required.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  63. Whatever happened to XP??? by jarnot · · Score: 2, Interesting

    Why not call it Windows XP Server? Makes more sense than calling in Windows 2003 Server.

    --
    -------------------------

    slashdot@com.jarnot (swap the domain)

    1. Re:Whatever happened to XP??? by Anonymous Coward · · Score: 0
      Why not call it Windows XP Server?

      Windows XP Server? That's just a stupid name. Are they going to have Windows XP Datacenter and Windows XP Advanced Server too? Why not just rename it Windows NT Server 6.0 while you're at it? God damn you're stupid.

  64. It's not gonna be just .NET at this rate... by intermodal · · Score: 2

    the more Microsoft keeps screwing its customers and changing up names on people once people figure out they don't want something, the sooner Microsoft will have to hide its products so people don't realize they're made by Microsoft....or maybe they're just too arrogant for that.

    --
    In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    1. Re:It's not gonna be just .NET at this rate... by smagruder · · Score: 2

      Maybe MS would get more respect for giving their products the "Macroshaft" moniker. They're giving us all the big screw, so why not?

      --
      Steve Magruder, Metro Foodist
  65. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  66. .NET and "security" by amoe · · Score: 1

    A thought occurs re .NET: I understand from an informative Ars Technica article that applications targeted to .NET are compiled to an intermediary bytecode format, a la Java. Now, I've heard from many sources that compiled Java class bytecode can be easily decompiled to source. Is this not fundamentally the case with any bytecode mechanism?

    Surely this will be a big concern for Microsoft. Ignoring their anti-OSS FUD, fact is most companies considering .NET probably don't want a sixteen year old kid publishing their top secret eternal life algorithm on the net. How are they (by which I mean Microsoft) going to stop this happening?

    --
    You look beautiful! Incidentally, my favourite artist is Picasso.
    1. Re:.NET and "security" by Meowing · · Score: 2

      Now, I've heard from many sources that compiled Java class bytecode can be easily decompiled to source. Is this not fundamentally the case with any bytecode mechanism?

      It's pretty much true true of any executable program. You can turn it into some kind of source code (at least assembly code if not the original higher level language). The .NET bytecode is in pretty much the same boat. If a dumb ol' computer can figure out what the instructions do, so can you.

      What you don't usually get from these reversal processes are the original variable names and comments, but given the output of some programmers this might even be a plus.

  67. Re:Predicted in the Kuro5hin interview with Adam B by Proc6 · · Score: 2
    I can't figure out why a dominatrix company like Microsoft would want "subscribers" anyway. I mean, think about it. The current model of selling Office for $600, then upgrading it every year or so works great. Thoes that can afford, pay, those that dont, keep using the old office for awhile, then get the new version with their next PC, or finally break down and buy it.

    With subscriptions, you're forcing your customer base to re-evaluate their licensing on a monthly or yearly basis. Each time you ask someone to re-evaluate something, you're risking getting a new answer, like, "fuck paying $50 a month for Office, Ill just try out this OpenOffice Ive heard so much about.". I can just see IT departments going "Well, we need to save the company some money this year. All of our Windows and Office licenses are up in Octoboer. We HAVE to do something, let's just switch to Linux/OOO."

    --

    I'm Rick James with mod points biatch!

  68. haha by autopr0n · · Score: 5, Funny

    From the slashdot blurb:

    Analysts are being quoted as saying that slapping .NET on so many Microsoft products has confused people as to what .NET actually means.

    The entirety of your comment:

    They are changing the name because people are getting confused about what .NET really is. It was a bad idea for Microsoft to try to add ".NET" to every single product they sell.

    And you got modded +3 Insightful! Not +5 yet, but just wait. All you did was change the wording around, and not even that much!

    what happened to the days would at least try to add tons of superfluous fluff around their restatements of the article when trying to karma whore.

    --
    autopr0n is like, down and stuff.
    1. Re:haha by bwalling · · Score: 2

      what happened to the days would at least try to add tons of superfluous fluff around their restatements of the article when trying to karma whore.

      I could care less about my Karma. The point of my post was stated entirely within the subject. /. just requires that you put some text in the body. The point was that this is hardly news.

    2. Re:haha by suwain_2 · · Score: 2

      The wording of the quote below and the main page are really quite similar.

      Slashdot article:
      "Analysts are being quoted as saying that slapping .NET on so many Microsoft products has confused people as to what .NET actually means."

      The post being discussed:
      "They are changing the name because people are getting confused about what .NET really is. It was a bad idea for Microsoft to try to add ".NET" to every single product they sell."

      It almost seems as if the author simply re-worded the original Slashdot post ever so slightly, and submitted it. You used to have to at least expand on something a bit before rewording it and getting it modded way up.

      (I can't believe I actually took the time to do that...)

      --
      ________________________________________________
      suwain_2 :: quality slashdot p
  69. Why didn't they do this right by Anonymous Coward · · Score: 0

    and change the name to something like Microsoft .NOT Server

  70. Microsoft: Pick one versioning scheme... by myov · · Score: 2

    ... and stick with it! I've had to tell many users that the upgrade from 98 is ME, not 2000. 2000 of course is the upgrade to NT. (officially anyways - ME is junk. And yes I know why 2000 is called 2000)

    Or, put the following in order based on release date:
    98SE, XP, 3.1, NT4, 95, .Net, 98, ME, NT 3.51, 2000.
    Bonus points for identifying the two different windows branches.

    --
    I use Macs to up my productivity, so up yours Microsoft!
    1. Re:Microsoft: Pick one versioning scheme... by elemental23 · · Score: 2

      3.1 -> 95 -> 98 -> ME -> XP

      NT3.51 -> NT4 -> 2000 -> XP -> ???

      --
      I like my women like my coffee... pale and bitter.
  71. iTools by Anonymous Coward · · Score: 0

    Sounds like something an optometrist uses.

  72. Thank GOD! by divide+overflow · · Score: 3, Funny


    I'm *SO* happy Microsoft is dropping the .NET from the server name. Every time a client would ask me what .NET was I would think:

    "Well, let's see...I can confuse him, anger him, or put him to sleep. Maybe I should fake a heart attack right now...."

  73. heh by autopr0n · · Score: 5, Funny

    What's funny is that Java's networking API is called java.net. You know, like Java.io, java.util, java.awt.image, etc.

    I've coded in java for years, and done lots of networking stuff in it, using java.net. But even then, during the height of the .net marketing push I was looking through the API for the first time in a while and saw "java.net" and it immediately made me think of .net, and made me wonder why there was .net support in J2SE. Then I came to my senses :P

    --
    autopr0n is like, down and stuff.
  74. NT by mrbrown1602 · · Score: 2, Insightful

    Why can't we just go back to the old naming method and call it "Windows NT Server" ? Life was so much easier back then!

  75. DropNet by Anonymous Coward · · Score: 0

    I guess the next name will be DropNet

  76. Microsoft's explanation by cwolves1 · · Score: 2, Informative

    FYI, this is microsoft's e-mail sent to all partners: Name Change for Windows .NET Server 2003 Announcement for Microsoft Partners Applicable To: All Microsoft Partners Worldwide SUMMARY The product name Microsoft(R) Windows(R) .NET Server 2003 is being changed, effective January 9, 2003, to "Windows Server 2003." Microsoft is making an effort to clarify the naming and branding strategy for .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products. The first product to be affected is Windows .NET Server 2003. The new name for the next version of Windows is "Windows Server 2003." This will not affect our time frame for launch, which is still planned for April 2003. DETAILS * We are pursuing an overall effort to clarify the naming and branding strategy around .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products. * The next version of Windows Server will be formally called "Windows Server 2003." The reason for this is to simplify the product's naming and reconcile it with our branding strategy for .NET. * "Windows Server 2003" will carry the "Microsoft .NET Connected" logo indicating its ability to easily and consistently connect disparate information, systems, and devices to meet customers' people and business needs (regardless of underlying platform or programming language). This logo is also available for use by our partners who are building solutions on the Microsoft platform to help customers identify solutions and products that support standards-based interoperability. * The more complete integration of .NET Web services and products is one of several major enhancements in "Windows Server 2003" -- all aimed at providing a highly connected, productive, and dependable infrastructure with excellent economic value for our customers. QUESTIONS & ANSWERS Q) Why the name change? A) In response to customer and partner feedback to provide clarity around our .NET strategy and programs. Specifically, we are moving toward a branding approach where ".NET Connected" is the way we communicate our products (and our partners' products) that enable customers to easily and consistently connect disparate information, systems and devices to meet their people and business needs, regardless of underlying platform or programming languages. Q) Why make this change now? A) Product naming, features, etc. are never final until the product ships -- this is both in response to customer feedback as well as part of a larger effort to provide clarity for customers and partners interested in affiliating with and benefiting from Microsoft .NET. Q) What changes technically in the Windows Server 2003 product as a result of this name change? A) There are no feature changes in the product. This is a naming change, and does not affect the functionality of the product in any way. Q) Will this cause a slip in the Windows Server 2003 product schedule? A) No -- we remain on track for a worldwide launch of "Windows Server 2003" in April 2003. Q) Is this an indication that Microsoft is backing away from .NET? A) Quite the opposite -- "Windows Server 2003" is a major step forward in our effort to provide a highly connected, productive, and dependable infrastructure with excellent economic value for our customers. "Windows Server 2003," with integration of the Microsoft .NET Framework, UDDI services, and other XML Web services support has set the industry bar for Web service development and performance -- combined with the new security, scalability, and performance of "Windows Server 2003" and we are delivering a platform optimized for the next generation of enterprise computing.

  77. Not news to us... by siskbc · · Score: 2
    ...but it is certainly news to see mainstream media, not just ZDNET but ABC frikkin' news picking up on this. Remember, random idiots don't read slashdot. That, I believe, is significant.

    And what do you mean *getting* confused? Was there ever a time when the .NOT marketing message was clear?

    --

    -Looking for a job as a materials chemist or multivariat

  78. You're missing the funniest part - the early days! by CrystalFalcon · · Score: 2

    Windows versions, listed (roughly) in order:

    1.03 (I actually have originals of this...)
    2.00
    286 (at which point "2.00" was renamed "86")
    386
    3.00
    3.1
    3.11
    95 (this has nothing to do with the "86" number used previously)
    NT3.51 (a different number series from 3.11, so why start at 3.51?)
    NT4
    98
    2000
    ME
    XP

  79. Microsoft announced this by lseltzer · · Score: 2

    http://www.microsoft.com/WindowsServer2003

  80. hence the inherent problem with palladium by GePS · · Score: 1

    (aside from the poor impersonation of an element for a name)

    If MS goes ahead with Palladium, I'll be keeping my eye out for the first virus to fool the OS into rejecting every app, regardless of signature. Perfect DOS attack. Can't do anything but reinstall from the installation media, if your DRM bios will let you that is...

    This is the main problem with this idea, the owner of the computer no longer has root access to their own machine with this DRM (emphasis on management) software. Ultimately, regardless of the level of knowledge, you cannot change certain settings/fix certain problems because of the micro-micro-kernel that's playing in the backgroung with read and write protection.

  81. MS seems to be making errors in judgement. by SphynxSR · · Score: 1

    It seems to me that Microsoft is making a lot more errors in judgement. The reality is you can't own or control everything. It will always fail. Generally it fails from the inside out. MS has gotten to big and it is trying to control very small things. It is getting to the point where they looking at to many little things today. They are also playing playing catch up with in the public relations game. And that is hurting them. They used to have very creative companys working for them, but now it seems they are just throwing money at the problem areas they see. Take IE, they never really advertised that product. They through money into it and put it in their operating system. Boom most people used, because it was there. MS has really lost their focus. Yea, they a lot of control over government and the US legal system. But little by little that is changing.

    --

    I don't suffer from insanity, I enjoy every minute of it.
  82. The .net framework a dead-born? by Anonymous Coward · · Score: 0

    The .net wave a flop ... if you ask this one year ago, people could have never think such a question could be up to date. But today it is !

    What have change within a year ?

    By acquiring the Rational XDE, the main .net supporter (aside MS itself), IBM has cut the left arm.

    By suiting to court MS to force them to put Java on their next OS and win the flag, Sun cut the right arm.

    Now there is a body left, and MS just did the funeral by removing the .net preffix to its next OS !

    Why do i care of .net ask users,developpers and architects ? I mean we've got stuff running : VB/Delphi for simple stuff, Java for entrerprise and portable stuff !

    Any pragmatic people now agree that .net framework (the stuff that compete with Java) is doomed to be a dead body within the next year ... but has MS put bucks in the .net suffix, they certainly want their money back !!!

    Maybe they could do a Intellipoint.net ? :o)

  83. Microsoft's New Competition to Slashdot by Anonymous Coward · · Score: 0

    Slash.NET

    I'm worrying and so should you.

  84. From the horse's mouth by Crash+Gordon · · Score: 1

    It says at the end it can be forwarded, so here goes:

    (Humor note: I had to do some editing because, as originally formatted, it tripped Slashdot's "Lameness filter :-)

    Name Change for Windows .NET Server 2003
    Announcement for Microsoft Partners

    Applicable To: All Microsoft Partners Worldwide

    SUMMARY

    The product name Microsoft(R) Windows(R) .NET Server 2003 is being changed, effective January 9, 2003, to "Windows Server 2003." Microsoft is making an effort to clarify the naming and branding strategy for .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products. The first product to be affected is Windows .NET Server 2003. The new name for the next version of Windows is "Windows Server 2003." This will not affect our time frame for launch, which is still planned for April 2003.

    DETAILS

    * We are pursuing an overall effort to clarify the naming and branding strategy around .NET. As support for Web services becomes intrinsic across our entire product line, we are moving toward a consistent naming and branding strategy to better enable partners to affiliate with this strategy and customers to identify .NET-enabled products.

    * The next version of Windows Server will be formally called "Windows Server 2003." The reason for this is to simplify the product's naming and reconcile it with our branding strategy or .NET.

    * "Windows Server 2003" will carry the "Microsoft .NET Connected" logo indicating its ability to easily and consistently connect disparate information, systems, and devices to meet customers' people and business needs (regardless of underlying platform or programming language). This logo is also available for use by our partners who are building solutions on the Microsoft platform to help customers identify solutions and products that support standards-based interoperability.

    * The more complete integration of .NET Web services and products is one of several major enhancements in "Windows Server 2003" -- all aimed at providing a highly connected, productive, and dependable infrastructure with excellent economic value for our customers.

    QUESTIONS & ANSWERS

    Q) Why the name change?
    A) In response to customer and partner feedback to provide clarity around our .NET strategy and programs. Specifically, we are moving toward a branding approach where ".NET Connected" is the way we communicate our products (and our partners' products) that enable customers to easily and consistently connect disparate information, systems and devices to meet their people and business needs, regardless of underlying platform or programming languages.

    Q) Why make this change now?
    A) Product naming, features, etc. are never final until the product ships -- this is both in response to customer feedback as well as part of a larger effort to provide clarity for customers and partners interested in affiliating with and benefiting from Microsoft .NET.

    Q) What changes technically in the Windows Server 2003 product as a result of this name change?
    A) There are no feature changes in the product. This is a naming change, and does not affect the functionality of the product in any way.

    Q) Will this cause a slip in the Windows Server 2003 product schedule?
    A) No -- we remain on track for a worldwide launch of "Windows Server 2003" in April 2003.

    Q) Is this an indication that Microsoft is backing away from .NET?
    A) Quite the opposite -- "Windows Server 2003" is a major step forward in our effort to provide a highly connected, productive, and dependable infrastructure with excellent economic value for our customers. "Windows Server 2003," with integration of the Microsoft .NET Framework, UDDI services, and other XML Web services support has set the industry bar for Web service development and performance -- combined with the new security, scalability, and performance of "Windows Server 2003" and we are delivering a platform optimized for the next generation of enterprise computing.

    Microsoft Communities is your launching pad for communicating online with peers and experts about Microsoft products, technologies, and services:
    http://communities.microsoft.com/home/d efault.asp

    How to use this mailing list

    To cancel your subscription to this newsletter, either click mailto:(mumble)@Newsletters.Microsoft.com?subject= UNSUBSCRIBE to send an unsubscribe e-mail or reply to this message with the word UNSUBSCRIBE in the Subject line. To stop all e-mail newsletters from microsoft.com, either click
    mailto:(mumble)@Newsletters.Microsoft.com?s ubject=STOPMAIL to send your request or reply to this message with the word STOPMAIL in the Subject Line. You can also unsubscribe at http://www.microsoft.com/misc/unsubscribe.htm. You can manage all your Microsoft.com communication preferences from this site.

    THIS DOCUMENT AND OTHER DOCUMENTS PROVIDED PURSUANT TO THIS PROGRAM ARE FOR INFORMATIONAL PURPOSES ONLY. The information type should not be interpreted to be a commitment on the part of Microsoft and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. INFORMATION PROVIDED IN THIS DOCUMENT IS PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND. The user assumes the entire risk as to the accuracy and the use of this document.

    microsoft.com newsletter e-mail may be copied and distributed subject to the following conditions:
    1. All text must be copied without modification and all pages must be included
    2. All copies must contain Microsoft's copyright notice and any other notices provided therein
    3. This document may not be distributed for profit

  85. PLEASE, THE IN SOVIET RUSSIA JOKES ARE ... by JuddN · · Score: 0, Offtopic

    ... getting a bit monotonous now. It was funny for a while, but now its just tragic. Every single topic that comes up has one now. How long must this go on ?

    1. Re:PLEASE, THE IN SOVIET RUSSIA JOKES ARE ... by JuddN · · Score: 0, Offtopic
      At least as long as the "ALL YOUR BASE" jokes did, dude.

      Great, so we can all look forward to a few more years of predictable ISR jokes. Maybe Someone will set up an ISR bot to generate them automatically ...

  86. year number is convenient by peter303 · · Score: 2

    OUr company does approximately three year cycles. It names a a year about three years in the future, so it has shipped at least one year by the time that year has rolled around. For example "2002" and "2005". In 2004 the nervouse customers feel "sage" buying version 2002.4. The earlier adopters can buy 2005.1.

  87. Not only that.... by siskbc · · Score: 1
    But dammit, that's not even a troll, ya know? If anything, it's flamebait. But like you say, the poor bastard makes a good point.

    Hey, is there any way to make moderators take a reading comprehension test about the article before they mark some redundant crap post as insightful?

    --

    -Looking for a job as a materials chemist or multivariat

    1. Re:Not only that.... by karmawarrior · · Score: 2
      It's like the old joke: The great thing about America is that anyone can become President - but the bad thing about that is that anyone can become President.

      Slashdot is like that. Anyone can become moderator - as long as they haven't been unlucky in metamoderation (which many of us who have always tried to be fair have) and moderation ultimately favours the trolls who set up a new account every week, post karma whoring stuff to raise their karma and then moderate according to opinions rather than to whether articles are any good.

      Dealing with this issue would involve an overhaul of the Slashdot moderation system, but therein lies a dialema: while moderators who abuse the system have the upper hand, those who would do a good job are modded so that they can't ever get the karma necessary to moderate. Worse, the abusers have multiple metamoderation accounts too and can get good moderators kicked out of the system altogether.

      This quagmire of poor moderators destroying the opportunity for good moderators to prevail will not disappear by itself. Resources need to be devoted, and unless people are prepared to actually act, not just talk about it on Slashdot, nothing will ever get done. Apathy is not an option.

      You can help by getting off your rear and writing to your congressman or senator. Tell them that Slashdot is important to you, but that good moderation is a necessity. Tell them that you appreciate the work being done to improve Slashdot's moderation system by Rob Malda and others, but that if the problem of poor moderators being out of touch and out of control is not resolved, you will be forced to use less and less secure and intelligently designed alternatives. Let them know that SMP may make or break whether you can efficiently deploy OpenBSD on your workstations and servers. Explain the concerns you have about freedom, openness, and choice, and how poor moderation harms all three. Let them know that this is an issue that effects YOU directly, that YOU vote, and that your vote will be influenced, indeed dependent, on their policies on Slashdot moderation.

      You CAN make a difference. Don't treat voting as a right, treat it as a duty. Keep informed, keep your political representatives informed on how you feel. And, most importantly of all, vote.

      --
      KMSMA (WWBD?)
  88. Palladium killing... by Anonymous Coward · · Score: 0

    Everyone is complaining that Palladium will kill open source on Win32

    Umm, I think that it's what will simply kill Win32. Period. Or at least kill its viability amongst Win32's current crop of consumers.

  89. Look Out, Server Vendors! by Thoguth · · Score: 1

    Judging by what MS is currently doing in courts with the term "Windows," it's only a matter of time before they claim ownership of the term "Server," and force anybody else using the term to change their name.

    --
    The requested URL /iframe/sig.html was not found on this server.
  90. Somebody please mod parent to funny. by Anonymous Coward · · Score: 0

    Because by now that question truly is funny... in the similar kind of humor in the original Saturday Night Live skits... or Monty Python's "Spam" or the "Knights who Say..."

  91. .net confusion? by ctve · · Score: 1

    It could of course be that software development tools have reached a sufficient level of maturity that people don't want anything more than VB5 or VB6. I have this argument with some geeks - they say "ah, but it does better cross-language interoperability", to which I say "and what was COM then, and why aren't MS simply improving COM". What can you not do to serve general business requirements with VB6 and SQL Server? People should concentrate less on getting new tools, and more on how to use existing tools better for their purposes - and maybe spend more time on analysis and design.

  92. My personal confusion... by Wampus+Aurelius · · Score: 1

    ...with .NET came from the commercials. Until I read today's Slashdot blurb about .NET, I thought it was all about jacking up wine prices after breaking your entire inventory.

  93. XP has already become... by Anonymous Coward · · Score: 0

    ...a bad name in the realm of corporate network administrators who have been having incessant trouble with making it (XP Pro workstation) work on the enterprise network with all the "legacy" win32 apps they still have to run.... and are switching back to W2K Pro workstation in droves. And MS doesn't want you to know that ugly truth.

  94. Rant on bro'... by Anonymous Coward · · Score: 0

    ... but you're preaching to the choir here.

  95. Two Questions [Re:Confusion?] by Anonymous Coward · · Score: 0

    Why would people buy it?

    Why would hw manufacturers support it?

  96. GOATSEX LINK IN PARENT!!!!!1 by Anonymous Coward · · Score: 0

    Please mod down so others don't click on this goatsex link thats so popular with trolls. Thank you.

  97. The cats out of the bag......... by chickensdelight · · Score: 2, Interesting

    I was also confused over the .NET strategy and then I read this artical on osnews.com http://www.osnews.com/story.php?news_id=686.

    To quote some of the artical for those who cant be bothered to go.

    "NET is a new way of working things out when using your computer. .NET the Framework is a collection of new APIs, programming languages and development tools that serve this "new way" of doing things. The new APIs are highly object-oriented, and the objects used are accessible by any supported language (VB.NET, ASP.NET, C/C++/C# and recently, even Java). This is a pretty revolutionary feature, having objects accessible by any language.

    With .NET's new APIs and libraries, applications are just hosts for a series of objects. Now you can load a given functionality found in any object to any .NET application. For example, if you are writing a Microsoft Word document and you insert an image, you might want to apply a certain filter to that image before finishing your document. Word, however, is not really an image manipulation application. Well, with .NET-enabled applications you can load a certain functionality from another installed application (or more importantly, through the web!), perform the specific function and save down your Word document locally or remotely. The thing is, applications are not simple applications anymore. They are hosts of a larger database of functionalities that they can be loaded at any time (for a fee or for free) through the web or locally. Similar feature-set is possible through Corba or OLE, as I said, but they are not standardized, they are difficult to integrate (a real headache for programmers), and they are not cross-platform."

    Given the posibilites ,new revenue streems to continue Microsoft growth, and the winning of OS wars (.Net for the Linux kernal) it would seem a big mistake on Microsoft's part to not fully support this way of working.

    This is a nice idea however and if Microsoft dosn't persue this new strategy some one else will e.g. IBM for example ( just go to google and type Globus).

  98. Wow by zBoD · · Score: 1


    > Obiwan Kenobi points out a similar article at ENT News


    Wow Jedi *do* read slashdot after all!

    --
    BoD
  99. Top 5 Rejected Replacement Names for .NET Server by serutan · · Score: 1

    SlashNET Server
    IIS++
    Microsoft VirusLoader
    Security Update Collector System (SUCS)
    Haxxor Gateway 2003

    heh-heh

  100. A little fun by drnomad · · Score: 2

    I made this page for fun more than a year ago: http://home.zonnet.nl/dropdotnet/

  101. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  102. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  103. That still doesn't mean by hackwrench · · Score: 1

    The .NET features they wanted are in the product.

  104. In the two letter tradition of "NT" and "XP"... by ConceptJunkie · · Score: 2

    The next version will be "Windows FU".

    --
    You are in a maze of twisty little passages, all alike.
    1. Re:In the two letter tradition of "NT" and "XP"... by mrkurt · · Score: 2

      Do you pronounce that as "Windows F-U" or "Windows Fu" as in Kung Fu? :P

      --
      Always look on the briight side of life! (whistle, whistle)
    2. Re:In the two letter tradition of "NT" and "XP"... by ConceptJunkie · · Score: 2

      Well, this is Microsoft. They don't have much Fu, and they always have a F-U attitude.

      I had the opportunity to work with an ex-Microsoft developer for a few months. He was incredibly sharp and had worked on the NT kernel and SQL Server in his 6 years at MS. I gave him a hard time about MS, much of which he agreed with. His reponse to my many questions of "Why is so-and-so so bad?" or "Why doesn't X work well?" is that "The smart people weren't working on that."

      I suggested that given Microsoft's size and resources they should have enough smart people to go around, but he said that wasn't true.

      --
      You are in a maze of twisty little passages, all alike.
    3. Re:In the two letter tradition of "NT" and "XP"... by WetCat · · Score: 1

      In Soviet Russia "XP" reads as "KhhhR" and associates either with snoring or with swine...

    4. Re:In the two letter tradition of "NT" and "XP"... by Anonymous Coward · · Score: 0
      His reponse to my many questions of "Why is so-and-so so bad?" or "Why doesn't X work well?" is that "The smart people weren't working on that."
      So, a developer works for a company from which most products are rather slow and bloated, and when asked why these products are slow and bloated, he responds, "Nothing to do with me -- I only worked on the good software!"

      You then cite the NT kernel and SQL server as products he worked on, these being two fair examples of inferior products vs the competition.

      I'm guessing you need a certain attitude to work for MS, and it shows.

  105. I suggest... by Anonymous Coward · · Score: 0

    ".failure"

  106. oops by the_2nd_coming · · Score: 1

    looks liek MS made a mis-step in betting the company on .NET back in 98.

    --



    I am the Alpha and the Omega-3
    1. Re:oops by devleopard · · Score: 2, Informative

      Because they renamed the product? I wish everyone who pretended to know anything about .NET would read the excellent article over at Ars Technica. At the same time, maybe the Microsoft marketing machine should read it as well. I'm sick of hearing people say that .NET is "software as a service", "Hailstorm", or the server technology. Other than having the classes loaded, the server is as much .NET as Solaris is Java. If Microsoft can get off of the buzzwords, .NET developers will have be able to establish their identity - currently, ".NET programmer" is about as specific as "GNU programmer".

      Hey! He's a .NET/GNU programmer, he can do _____________ (insert one of the many technologies associated with .NET/GNU here)

      --
      The best thing about a boolean is even if you are wrong, you are only off by a bit.
  107. Re:Top 5 Rejected Replacement Names for .NET Serve by Anonymous Coward · · Score: 0

    Don't quit your day job. :)

  108. Puzzled. by miguel · · Score: 3, Insightful

    I am puzzled that a project rename would generate 298 posts in Slashdot. I guess everyone had an opinion.

    1. Re:Puzzled. by Anonymous Coward · · Score: 0
      Op down parent, seeks to destroy Free software movement by seducing GNUsers over to .NET.

      (Meanwhile, I am puzzled that anyone so anal as to worry about number of comments posted on a particular Slashdot topic then contributes his own comment just to express the worry. Remember kids, the parent was posted by the guy who heads the .NET-on-Unix project, just so you know what kind of attitude this guy has.)

  109. what is .NET? by Anonymous Coward · · Score: 0

    It's what you use to catch the .FISH

  110. Confusing names by martin-boundary · · Score: 1

    Personally, I like to call DRM the Antitrusted Computing Initiative. It captures the goals of Microsoft in this case quite well, I think, and most of all doesn't mislead people into thinking "security" refers to theirs as opposed to Microsoft's in this case.

  111. C like language with basic syntax changes by Anonymous Coward · · Score: 0

    I'm excited the new generation of MS programmers won't even know how a C switch statement works.

  112. Disturbing encounter by djupedal · · Score: 3, Interesting

    I walked into the dimly lit room and looked around. It seemed something was trying to gain my attention, but in the darkness, everything seemed to blend into one shapeless form or another.

    As my eyes adjusted to the low light, I began to make out a scribbling on the far wall...dot not....dot nut....dot nat....dot nit....dot net??? I couldn't make it out and it worried me. Dot what?

    I walked over and traced the ragged letters with my finger tips, trying to imagine who did this...and why. The scrawl was halting and labored. The only thing I could be sure of was that, whomever wrote this message, they were clearly in pain.

    I backed out of the room and tried in vain to clear my head...what where they trying to say? Who was behind this cry? Was it a warning to stay away or a dieing request for help?

    I went on about my rounds...the day shift would be on soon, and I'd have to return to the future. I'd let them work on this one. I'd heard they had another new open source tool that was made just to analyze these. It was too early and too much for me to consider yet another message from the other side...from the past. The last one took part of my soul, and I need the few little fragments that are left...

  113. Re:Puzzled???? Really? by Anonymous Coward · · Score: 0

    Actually, tons of people are puzzled by the fact that you are a secret employee of Microsoft and are unwilling to admit it.

    Now *thats* puzzling!!

  114. And - you can't run your own code on the system by lukme · · Score: 1

    Forget about doing any software development at home -- you won't be given the keys to sign it. Additionaly, forget about running your older software. Since it is unsigned, you won't be able to run it. I sence a boon at microsoft. This could make it possible to kill all of the small software businesses.

    1. Re:And - you can't run your own code on the system by Corrado · · Score: 2

      Nah, you just have to purchase some key-signing software from - - - - Microsoft. Wow, they get you coming and going agian! :)

      --
      KangarooBox - We make IT simple!
  115. Branding by Gortbusters.org · · Score: 1

    Branding is a major part of any business. Sometimes you might have a company with a boring name, but come up with a really neat name for their product like CodeVortex (you get the point).

    On the other hand, if you want to accent the name of the company... you might just call something Microsoft Windows.. or the IBM 4000 server.

    --
    --------
    Free your mind.
  116. microsoft.com is right, not .net by InfiniteWisdom · · Score: 1

    Finally they've come to their senses.... of course they should stick with microsoft.com.... microsoft.net is ust plain wrong.

  117. What's in a name? by benjiboo · · Score: 2, Interesting

    The thing is, none of the last round of server products were .NET in anything other than name anyway. They were developed in the DNA world - pre-2000 (e.g last versions of Commerce, Biztalk and SQL Server's 2000) which was before MS even began this .NET rebranding excercise. Repackaging them all as .NET only served to confuse people at the time so reverting these guys could be a good thing.... But it sounds like they are dropping the names in the next generation of servers... which are more likeley to have a .NET flavour - Go figure!

    --
    Vacancy for signature. Apply within.
  118. Excellent "What is .NET" Whitepaper at ARS by nazgul000 · · Score: 3, Informative

    I see many "What is .NET" posts here. The best single whitepaper I've seen on .NET is by the Ars Technica folks:

    Microsoft .NET at Ars Technica

    cheers.

    1. Re:Excellent "What is .NET" Whitepaper at ARS by lizardbox · · Score: 1

      Yes, a very good whitepaper, technically speaking. However, it completely disregards all political and economical implecations involved with the whole .NET technology, which are by no means marginal.

      --
      -Carpe Diem (lizardbox)
  119. Finally by miketang16 · · Score: 2, Interesting

    This may be considered redundant, but ever since MS came up with this whole .NET thing.. i've been thinking.. OK.. sounds waaayy too much like they're trying to do the whole 'Synapse' thing. (Antitrust) About time they wised up.

    --
    -------
    "In times of universal deceit, telling the truth becomes a revolutionary act."
    -- George Orwell
  120. Mod parent FUNNY! by Anonymous Coward · · Score: 0

    That is the most hilarious thing I've seen in ages on Slashdot.

    Yes, even better than a Beowulf cluster of Natalie Portman. Mmmmm...

  121. Explorer by Anonymous Coward · · Score: 0

    I've said for years that they should stop naming everything 'explorer':

    a) the windows file manager: "Windows Explorer"

    b) the windows shell "explorer"

    c) internet browser: "Explorer"

    I guess when the get a name stuck in thier heads, they stick with it.

  122. Visual J++ by Latent+Heat · · Score: 2

    C# is a lot, lot like Microsoft J++: think of J++ as C# version 0.9.

    1. Re:Visual J++ by Anonymous Coward · · Score: 0

      Not at all. I write C# apps and it is certainly not the next J++.

      C# has similarities to Java, but their are some very distinct differences between the two, such as the .Net namespaces, new keywords like foreach or ref that allow developers enumerate objects in collections more easily than in, or do simulation of pointers as parameters much more easily than C++. Dynamic arrays are so much easier to do in C# using the ArrayList object...I could go on, but I'm blabbering now. :)

  123. Re:You're missing the funniest part - the early da by cant_get_a_good_nick · · Score: 2

    You forgot NT 3.11, and NT 3.5

    Even though NT was 1.0, MS didn't want the 1.0 stigma (specially with MS's 1.0 history) so called it NT 3.11, it's justification was that NT was at the smae level as Windows, so it deserved it. Silly since it's either more advanced (NT based on microkernel, 32-bit, protected memory) or much greener (a 1.0 release).

  124. The Real Del by Bird+Watcher · · Score: 3, Informative

    Ultimately the meaning behind any marketing term is somewhat arbitrary. When Apple came out with the Apple name, it initially didn't mean anything. Over the years it came to mean a lot in the minds of many people. That's kind of what a brand name is all about, right? .NET is the same thing only MS has done a very bad job defining it. Re-naming the Windows .net server is (perhaps) a step in the right direction. If you look at the leaked Q&A from the announcement, it seems very clear to me what they're doing. I'll try to explain in simple terms.

    1. In the beginning they announced .NET as a web services initiative - basically a way of writing software that uses XML, SOAP, WSDL etc. to allow apps to interoperate. A poor mans COM.

    2. The a bunch of marketing goofs started attaching the name to lots of things - most importantly the .net framework.

    3. The .net framework is - for all intensive purposes three things. First, it's a new programming model for Windows based on the common language runtime that makes it much easier to write secure, stable Windows appps. It also includes a new version of ASP that makes building web-based easier. It also includes facilities that for building XML web services and a bunch of new class libraries for Windows and web apps.

    4. The big mistake they made was putting .net into the name of the framework because it confused everyone. To people who can't read the tea leaves, it suggests that any appliacation built ising the framework is a ".net app." In reality, most of the apps built using the .net framework today are just better, more secure Windows apps or ASP/web-based apps.

    With the announcement they said in clear terms that the .net brand is about Web services interop. They obviously still want people to build Windows apps and are making it easier to do so than it has been with Win32/MFC etc. So they're building web services capability deep into their platform -into Windows, into Office I'm sure and into all of their server apps.

    For developers this is a beautiful thing. They can take it or leave it. They choose to build on Windows based on its merits. Market opportunity, ease of development or whatever. Some may ultimately choose to build on Windows because Windows has good XML web services support.

    I think MS's strategy is to continue to make Windows as good as they can and compete with J2 by providing superior support for web services. The theory (just a theory) is that if web services mature then developers can choose whatever platform they want and rely on web services to stitch things together across platforms. This could be a good strategy because it undermines the Java-only argument. No need to build apps on a single platform (middleware platform in this case) because web services provide good cross plat interop.

    So, the bottom line is that MS is narrowing what .net is to web services/interop. The .net framework programming model/CLR etc is, fundamentally a Windows thing. No surprise, right?

    That said, MS is taking parts of the .net framework/CLR programming model and porting it to other platforms. That way they can try to lure ISV's to build "Windows apps" that run on other platforms. I know. Sounds confusing but I think this is accurate.

    This is way MS, IBM and other companies are so excited about web services and why others - particularly SUN, have been a little slow on the uptake. Although this is overly simplistic, Sun/the J2 crowd basically want everything to be Java/J2. IBM will sell anything to anyone. MS wants to make Windows the most attractive platform.

    Gosh, this almost sounds like good old competition to me.

    Sorry for the ramble but, mark my words, this is the correct interpretation.

    1. Re:The Real Del by Bird+Watcher · · Score: 2, Funny

      I just re-read my post and I sound incredibly arrogant. Sorry! But I guess that's not unusual on slasdot. My POV is based partly on good info, not just random opinion.

      Cheers

    2. Re:The Real Del by Junta · · Score: 1

      Offtopic, but fyi, the phrase 'for all intensive purposes' doesn't make much sense. I believe you should have said 'for all intents and purposes', which is the common phrase which sounds most like what you said. Though redundant, it at least makes sense.

      Someone even has a web page dedicated to this very type of error:
      http://www.wsu.edu:8080/~brians/errors/int ensive.h tml

      --
      XML is like violence. If it doesn't solve the problem, use more.
  125. no one will read it, but by Anonymous Coward · · Score: 0
    Having worked with .NET C# and J# recently, there are some good and bad things. First off, the performance is equivalent to JDK1.1.4. Second is there are a lot of nice things about C#, like a cleaner OO implementation than C++. The bad thing is C++ kept a lot of the confusing, difficult and error proned C++-isms.

    I know this from running side by side comparison of different apps written in Java, J# and C#. Jdk1.4.x beats C#. But then again it's the first release, so matching jdk1.1.4/jdk1.2 performance isn't bad. It's probably good enough for most apps. Some of the things that are annoying is System.DateTime isn't accurate for millisecond and submillisecond timing. For that you have to use other windows native libraries.

  126. Nothing new here - remember ActiveX by TekPolitik · · Score: 4, Insightful

    They did this with ActiveX too. For a while, everybody at MS said their project was part of the ActiveX initiative. Then they scaled back the use of the term

    This sort of thing is not uncommon in software companies - they have a new project that becomes flavour of the month, and everybod will try to reclassify their project to fit within the new project. If the new project has attributes A, B and C, a project with attributes C, D and E will claim to be part of the trendy project because of the overlap at C, when the real value of the trendy project is the combination of A, B and C.

    The other thing that happens with new projects at software companies is that the entire sales force will want to be selling the new project and ignoring everything else. My theory here is that the salespeople have such tiny brains they can't deal with more than one project at once. The other projects languish for a time, which creates another incentive for them to reclassify themselves into the trendy project's area. This can be a real problem for the company because their staple lines stop selling as much since the salespeople aren't pushing them, and the new trendy thing is either not ready or hasn't built enough following to take up the slack.

  127. And I can't spell "Deal" oops. by Bird+Watcher · · Score: 1

    Sorry. Just got excited.

  128. This really sucks by slickwillie · · Score: 3, Funny

    Now I have to stop saying "Just say .NYET!".

  129. This thread says it all. by Anonymous Coward · · Score: 0

    Why is Microsoft changing the name? Slashdot very beautifully illustrates why. Most people don't really know what it is and attribute it to a ton of other things which are only marginally related to .NET, if at all. .NET is a multilanguage development framework designed to replace the c-centric Win32. It takes many of the ideas of COM, mixes it with ideas from Java, Delphi, and a dozen other places, and comes up with a component-driven environment. This framework has such things as XML built deeply into the core, which, along with Microsoft's ASP.NET, makes it a formidable WebServices platform. WebServices aren't .NET, but they are a type of application you can develop on them. Notably I interop WebServices between .NET and Java often without issue; it's all very seamless.

  130. X.x by revxul · · Score: 1

    I miss the days when the name of the software was followed by a version number. But noooOO0OOoooo, we've gotta be all flashy and crap. This is what, NT6 or 7 or something? This whole drop-the-version-number-and-give-it-a-flashy-name- instead thing gives me a headache.

    --
    Truth, Just Us, And Hatred For All Mankind!
    1. Re:X.x by cookiepus · · Score: 1

      May I recomend you go to a doctor? If it pains you to remember that XP came after 2000, there's something wrong somewhere.

  131. I thought .Net meant Bill Gates underwear by Anonymous Coward · · Score: 0

    I thought that .Net meant Bill Gates Underwear Line
    Since the adoption of his underwear line is zero to nil I guess it is time to change the name and market it again.

    I guess lets hype it that it can wipe your bottom too and put condom on your tiny pee pe like Bill Gates.

    1. Re:I thought .Net meant Bill Gates underwear by Bird+Watcher · · Score: 1

      Thanks very much for raising the level of discourse...

  132. palladium functionality by Anonymous Coward · · Score: 0


    Essentially I like the idea of creating a system where you can physically guarantee short of physically modifiying hardware on the microchip level that a program will do "X"


    How does palladium guarantee that a program will do anything? all palladium does is ensure that microsoft-signed programs cannot be tampered with, not even by the person who owns them and the computer they're running on.

    And the "not even by the person who owns them" is the only new part. We've had all the rest of that for decades. On any modern operating system, a program running as user A cannot tamper with a program running as user B, unless some programmer made a mistake somewhere. But palladium is susceptbile to human error too. Another example, the java applet sandbox.

  133. Java has killed .Net by Anonymous Coward · · Score: 0

    Haha well we got the last laugh. .Net adoption is zero.

    Everey one is using Java.

    Linux will kill windows desktop too.

    Ahh there is a god.

    1. Re:Java has killed .Net by lizardbox · · Score: 1

      Last I checked, the open source community is not really after Windows and Micros~1. We're just out to develop better software. It has nothing to do with MS. Don't kill em, just offer something better.

      --
      -Carpe Diem (lizardbox)
  134. As usual, Redmond is one step ahead of ya'... by Anonymous Coward · · Score: 0

    It is likely that some managers heard of visual studio .net and immediately checked "visualstudio.net" to find out what the name of the latest version of visual studio was.

    http://visualstudio.net redirects to http://msdn.microsoft.com/vstudio/default.asp.

  135. .Net's new name is .Not (R.I.P .NET) by Anonymous Coward · · Score: 0

    M$ finally realized how buggy .Net is and renamed it .Not .

    R.I.P .NET

  136. Ok, I have a mod point left but... by digitalcowboy · · Score: 2

    I had to reply to this.

    That is great writing, my friend, in both style and substance. Not that I am by any means an expert.

    But, I'm no idiot either and, that sort of writing is (mostly) wasted on this board. Have you ever heard of casting pearls before swine?

    You should be published. Have you tried?

    If not, you should.

  137. Speaking of .NET by lizardbox · · Score: 1

    I've refreshed /. about 20 times, trying to get the "Microsoft .NET ad" I got earlier today when I was at work. Micros~1 can advertise on /. ? never knew that. Wish i'd taken a screen capture.

    --
    -Carpe Diem (lizardbox)
  138. Microsoft drops .NET!! by Anonymous Coward · · Score: 0

    I told you .NET wasn't a serious M$$$ strategy. They dropped it completely!!!

  139. .NET should really be called .NOT by spullum69 · · Score: 0, Flamebait

    microsoft (is) .NOT worth the money
    windows (is) .NOT a business server .NET lets bugs slip right through
    Office (is) .NOT an internet application (or very fast for that matter)
    Visual Studio (is) .NOT something new
    Windows (is) .NOT stable
    the Micro$oft XBux, it's .NOT even a threat to Playstation or Gamecube
    Microsoft (is) .NOT an innovator
    Microsoft (is) .NOT the answer
    Microsoft (is) .NOT an equal player in the industry
    Microsoft (is) .NOT to be trusted
    Windows (is) .NOT finished
    Windows (is) .NOT ready to ship
    Windows (is) .NOT user-friendly
    Windows (is) .NOT an original product (or even their own product)
    Windows (is) .NOT going to boot up this time
    Windows (is) .NOT secure

    product monikers for future M$ products: .SUX, .BILL (founder of M$ and what you pay to M$), .MS, .NT, .DOS (the real truth), .WIN .BLUE, .BUG -> my favorite

    let's try some of these out
    Microsoft Windows .BUG Server
    Microsoft Windows .BUG Home Edition
    Microsoft Windows (really is) .DOS
    Microsoft Plus! for Windows .BUG (more bugs 4 j00)
    Microsoft Windows .BILL 21st Century Edition 2003 .BUG -> OK, I'm done

    www.windows.blue (KABOOM!)

    --
    Shawn D. Pullum
  140. It doesn't make any sense... by MegaHamsterX · · Score: 2, Funny

    Microsoft marketing .NET is like ford running dumptruck commercials during the superbowl. It's a commercial product, if I need a compiler I know where to get it, if I need a tool I know where to go (I'll start in Redmond first).

    .NET has bombarded me from every direction, I usually keep up with MS stuff despite my dislike for them, I gave up on this, the term seems to mean everything Microsoft, but it then seems to mean specific things in certain instances. It's f&cking confusing.

    I half thought the MS marketeers were watching the smurfs and instead of smurf the used the word .NET

    New Smurf technology enabled my Smurf application with expanded communication using the Smurf framework on the Smurf advanced server.

  141. :) thanks by djupedal · · Score: 2
    In Japanese, the phrase is 'nekko ni-koban' - which means "coins to a cat..."

    I figure if street musicians can play in subways, I can drop bytes here:

    Published?
    • 50+ countries
    • 15+ languages
    • 10+ million printings per year for the last 4 years running.
    I'm a technical writer :)

    One of these days I'll find a publisher and get out of this rat race. If you know anyone, please tell me, thanks.
    1. Re::) thanks by Anonymous Coward · · Score: 0
      50+ countries
      15+ languages
      10+ million printings per year for the last 4 years running.
      Isn't web publishing just grand?
  142. A marketing fumble? by Anonymous Coward · · Score: 0

    All that money spent for no .net gain.

  143. Difference is... by SuperKendall · · Score: 4, Interesting

    C# is Java with the capitalization Gone Wrong.

    C++ is C++.

    C++ under .Net is C++ with "crippled" syntax - no templates, for example.

    I'm not saying that .Net and C# are nessicarily all bad, mind you. What I am saying is that in .Net, all roads lead to C# and other languages under .Net are really C# training wheels. You can choose to use the training wheels as long as you like, but if you want to really do anything you have to take them off someday...

    Part of that is because .Net is, like Java, very heavily library based (in that most anything you want to do involves a number of library calls from a fairly rich library) - and those lbraries are most naturally accessed in C#. When using other languages, they will have varying ranges of ease to access these libraries but C# is always there at the end of the curve beckoning you closer.

    For perhaps something more like what you were looking for, you might want to read Ten Top Traps in C# for C++ Programmers.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  144. Confusion with CE also by Anonymous Coward · · Score: 0

    When we received the early CE 4.0 Platform Builder kit, we noticed it was now called CE.Net. And there was a bright red sticker on the box that said .Net Compact Framework included.

    But it was all wrong, it had no .Net, no Compact Framework with it. This company needs to get its act together. Obviously marketing is in charge here, which is good news for the slashdot crowd.

  145. Come on this is old trick by Anonymous Coward · · Score: 0

    IIRC a prof teaching maeketing in college mentioned something like "It is a good marketing strategy to confuse the customers by flooding the market with similar products". May be applicabe in the case of software also. Just look at the LARGE number of products in the markets with miniscule differences in their contents advertised as "all new" "latest" "contains XXXX formula". The same old principle. Selling is selling

  146. slapping .NET by varslot · · Score: 1

    If slapping .NET on so many Microsoft products has confused people as to what .NET actually means, what effect will slapping 200x on so may Microsoft products do to the average consumer's understanding of natural numbers?

    --
    There arises from a bad and unapt formation of words a wonderful obstruction to the mind. (Francis Bacon)
  147. IBM did a sorta similiar thing with Domino by WrkActJob · · Score: 1

    Well, on a smaller scale. I think they tried to rebrand lotsa things as Notes or Domino...even though they had nuffink to do with N or D.

    The stock standard AS/400 http server suddenly became Domino or Notes. Confused everybody. Was dropped in a matter of weaks.

  148. .NET has failed consumers interest by Junkstyle · · Score: 1

    The reason they are changing its name is .NET hasn't given very many IT managers a hard on. .NET has had spectacular failures associated with it. They would be insane to label anything they wanted to sell .NET after all the negative press .NET has received.

  149. http://www.microsoft.net/ by Conspire · · Score: 2

    Well, when I go to http://www.microsoft.net/ I get the great words:

    "Smart Living See how new and future Microsoft products and technologies showcased at CES will help you have fun, keep in touch, and be entertained."

    So, from that, I guess:

    1. .net is about "smart living", whatever that means, or whatever Gill Gates thinks it means.......damn, gotta get rid of my dumb Linux, freebsd and Apple boxes, and bring back the dead MS boxes i used to run...

    2. I will be wearing a Microsoft watch sometime in the future......damn again, i really like my mechanical automatic Officine Panerai Militare...do I really have to have a Microsoft watch in order to live smart and keep in touch and be entertained and have fun?

    3. I will need a tablet PC.......damn...I just want the new Powerbook 17" G4, do I really need a table PC running XP? I hate XP...arg. Guess I will have to if i want to keep in touch, have fun and be entertained...

    4. My mobile phone will run windows........damn..I really like my Nokia....guess that does not keep me in touch, let me have fun, or entertain me...............

    I guess we all need Microsoft to have fun, keep in touch, and be entertained, that is what .net is all about, making everybody need Microsoft......

    --
    Real men don't need signitures!!!
  150. My favorites by UncleRage · · Score: 1

    My personal favorites were: .crash .gotcha .sucker
    and of course .allyourprocessesarebelongtous

    --
    #SickNotWeak
  151. Trusted scripts are available on Windows by spideyct · · Score: 1

    You've been able to create trusted scripts on Windows for a while now.

    Since Windows Scripting Host 5.6 at least.
  152. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  153. .NET is CORBA by Anonymous Coward · · Score: 0

    I.e. language-independent, but you don't have to write your own marshalling routines and stuff.

  154. Say No to FUD! SOAP is *not* a M$ application! by Anonymous Coward · · Score: 0

    Sheesh. It is very unfortunate that people who read too much of the M$ FUD & propaganda really go out and regurgitate this bs. Bill must just laugh his can off.

    Look my dear chap, XML is a metalanguage. It is *not* an application and language of .NET no matter what garbage M$ wants you to believe.

    SOAP is, well, here's what the letters stand for to give you a hint "Simple Object Access Protocol".

    The basic point here is that you can write SOAP apps, or use XML, or build web services in many many many languages. Python, Perl, Java, just to name a few. Read some of the great books and articles by folks like Brett McLaughlin and Doug Tidwell. Enlighten thyself!

  155. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  156. I'd have to second that... by cr0sh · · Score: 2

    You should look into fictional, tech-style writing. You have an excellent way with prose, and your short writing was a bit haunting, mixed in with hope - I loved it. Just something to consider - you have the knack.

    --
    Reason is the Path to God - Anon
  157. Why? by sean23007 · · Score: 1

    Does it really make a difference?

    --

    Lack of eloquence does not denote lack of intelligence, though they often coincide.
  158. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  159. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  160. /. user zoo by RudeDude · · Score: 1
    To: r

    Pardon my posting a reply in a story, but I have no other way of getting a note to you. Hopefully you will see this.

    When trying to go to my own user account a typo had me looking at user "r". You've posted some great comments and I decided to mark myself as your fan.

    Hopefully this crazy zoo system will help with the 'noise' level of comments on SlashDot; Because I must agree with you that I occaisonally consider giving up.

    --
    RudeDude
    Perl/Linux/PHP hacker