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
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.
in any case, the semantic shift of the label
My other car is a cons.
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.
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.
C# is Java with the capitalization Gone Wrong.
.Net is C++ with "crippled" syntax - no templates, for example.
.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...
.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.
C++ is C++.
C++ under
I'm not saying that
Part of that is because
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