views:

2343

answers:

12

I always wondered why Microsoft chose such a strange, search-engine-unfriendly name for such a great platform. Couldn't they have come up with something better?

Apparently the codename was NGWS:

Microsoft started development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). [Wikipedia]

Does anyone know why they chose the name .NET?

+12  A: 

interNET would be my guess

In the mid\late 90's Microsoft saw the internet as the Future and also felt they where a little late to the game. Thus Explorer being forced on people by being embedded in the OS(Which they are regretting now). Removing competitors such as Java from Windows AND a really over the top name like .NET to indicate there are now a web friendly company....

cgreeno
It was this because Microsoft envisioned networked services.
Daniel A. White
I think you mean "In the late 90's" They kind of flubbed the early and mid 90's.
Chris Lively
fair point all fixed :)
cgreeno
+36  A: 

.COM was taken.

Chris Lively
Funny, but not an answer. :|
Robert P
Ha ha +1 for that!
Shoban
Hm, maybe it's not even a joke. Who remembers Sun's "We are the dot in .com" of that time? They just wanted a dot, too ;)
markus
LOOOLLLLLLLLLLL
Andrei Rinea
Hahha classic .
Greg B
Because this answer appears to be pretty popular, I'm going to give a better explanation: Although my answer was somewhat tongue in cheek, @markus nailed the double entendre. Sun came out with the "we put the dot in dot-com" marketing campaign around 1999. At this time Microsoft was developing a product called NGWS. NGWS isn't very pronounceable and the marketing team wanted something with a bit more jingle. Also, from a marketing perspective it's easier to subvert a competitors campaign than introduce something new. So, with "dot-com" taken, NWGS was renamed in 2000 to .Net.
Chris Lively
+1  A: 

Since you're not going to look up the answer, neither am I :) But if I remember correctly, Microsoft was trying to play up the connectivity aspect of .Net. They've been trying to get "up to speed" with the whole Internet thing since Active Desktop, and have a history of goofy names and poorly thought out ideas. Not that .Net is a bad technology, I'm not saying that.

I will say, however, that .Net is one of the worst names I've ever come across. It's hard to search for and in no way communicates what the "product" is. If you remember the early days of .Net, there were plenty of articles and interviews and videos of Microsoft big wigs trying to explain what .Net was using big budget buzzwords... it didn't work well and for years people would still wonder what the hell it was. Even MFC was a better name because at least a programmer could recognize the components of the acronym.

Boden
It also didn't help that MS spent a while slapping ".NET" on the end of the name of any product that wasn't fast enough to get out of the way, regardless of whether it had anything to do with the .NET Framework or not.
Joel Mueller
Regarding "no way communicates what the 'product' is". The same can be said for pretty much all of those in the field. Consider Java, Pascal, Ruby, etc. Each of which have names that require you to know context to infer meaning.
Chris Lively
@chris but the name .NET can actually put you off because it's an existing thing in the IT arena. Can't say the same for Java unless you are saying programmers drink a lot of it. For me the name .NET definitely put me off looking at it seemed like just another web technology. I stuck with Java for a long time until it became much clearer.
PeteT
Yeah, it felt a lot like the marketing department got ahold of .NET and went for a consumer approach. I suppose they figured that the more people talk about .NET, regardless of whether they should be, the greater the chance that the CEOs/CTOs of the world will say, "hey, do we have that .NET stuff in our apps? Get it in there, that's what the people want!"
Boden
+4  A: 

The early marketing thrust of .NET was web services. .NET was supposed to make it easy both to write and consume web services. In particular, it was supposed to make it easier to call the web services that Microsoft was going to provide, and that everyone would then use: the ".NET My Services".

Of course, that fell apart very quickly, but the name remained. It was at least better than "COM++" or "ActiveXX".

John Saunders
+1. I think during very early days even ASP.NET was called ASP+.Here is an article written in July 2000:- http://archive.devx.com/asp/articles/ck072600/ck072600.asp
ydobonmai
@Ashish: you're right about "ASP+". That's why we have ".ASPX" files.
John Saunders
+1  A: 

It's the single stupidest name the marketing team could think of, and that's why they went with it. I can't explain it any other way.

Daniel Earwicker
+20  A: 

.NET is natural for Microsoft marketing to emphasis on the "Network"-ing aspect of its technologies and reacted to the marketing blitz by Sun Micro System in the late 1990 where the theme was "Network is the computer". The term "Dot-Com" was synonymous with the Internet that time, and "Dot-NET" was a play to that word.

I don't think it is a bad name at all, the problem was that Microsoft named so many products with the ".Net" nomenclature like .NET my services, Microsoft .NET Enterprise Servers where the latter had nothing to do with the Internet. It caused so much confusions. Only later Microsoft corrected itself by limiting .NET name to technologies related to Managed Runtime Framework.

Stanley Siu
remember the .NET Passport? I think that was the most confusing bit for users.
moogs
I remember being very confused by the .NET marketing. It meant everything and nothing. They would have saved a ton of problems if they just said "it is something like Java".
TomA
+1 for "it is something like Java"
ydobonmai
The .NET name put me off learning it for quite a while it seemed to have no focus as to what it was. I kept focused on Java for a lot longer because of it.
PeteT
Maybe this old article will be interesting: Gates: .Net Is 'Architecture For This Decade' InformationWeek 2002 http://bit.ly/dc3Wm6
Nick Martyshchenko
+5  A: 

I was a dev at Microsoft at the time, and I have no idea whose ass the name .NET was pulled from. Anyone I talked to thought it was a lousy name for all the reasons already enumerated. At least it's pronounceable, unlike NGWS.

George V. Reilly
NGWS is perfectly pronounceable! Think the word “penguins”, but without the the “pen” or the “n”—“nguis”!
notJim
@notJim Yeah and it sounds horrible!
billynomates
+10  A: 

it's called .NET so it wouldn’t show up in a Unix directory listing!

SteD
=))))))))))))))
Andrei Rinea
A: 

tel exact meaning of .net

ritika
platform for api
ritika
A: 

net means Network Enabled Technology . and some people say because everything can be accesed with help of DOT operator hence it was called .NET ... some one told me this answer am not sure until what extent is it correct

Vijju
-1: I don't know where you heard this, either. If _you_ don't know, then you shouldn't post it as being a fact.
John Saunders
On the other hand, even after the fact it makes more sense than many of the other possibilities. I suppose that's a vote against it being the correct answer...
mickeyf
A: 

Most of the person asked this thing that why .net is called .net and what is the significance of . over here? so, the answer is as dotnet is a collection of many languages. here .(dot) show the collection of 70+ languages which is used in visual studio's any version. while net refers to (network Embedded Technology) as we are flexible enough to make any sort of program which might run on network..one more reason is ther if u want to run any asp.net project on the server..will use the iis server which works as an local server to execute the web based program. so, that there is no need to create any other server..specifically for running a web based program...

Sarthak Sharma
-1: I have no idea where you got this, but it's not true.
John Saunders
-1 You have no idea what you are talking about
PeteT
A: 

Can believe the obvious reason isnt already answered?

Microsoft lost their case vs SUN who had developed JAVA. Microsoft wanted to push JAVA further forward and into Microsofts Windows environment, to allow it to run faster and utilize Windows better.

SUN saw the "badness" in another Microsoft only and wanted JAVA to stay true crossplatform. So after Microsoft lost the case, they removed the JAVA-VM from their Internet Explorer and now consumers had to download the client manually if they really wanted JAVA so badly.

In the background Microsoft had gained SO much insights in how JAVA was build and combined with their ideas, they "invented" .NET technology based on Microsoft platform. They also made it OpenSource, so that people could produce "legal copies" on other platforms if they wanted (MONO).

So... why is .NET called .NET ? well, the name "JAVA" was already occupied and the new name had to be very different because of lost case/court trials, eventhough the technologies behaves very similar.

(oooh, now I will probarbly get my head pulled of and placed on a stick somewhere by angry evangelists, so before that, just for your information people, I develop C#.NET solutions myself. Not JAVA, and every example I've seen on JAVA looks more or less the same. The only changes are some of the syntax + the API names)

EDIT

FFS... seems like some Microsoft Evangelists couldnt handle the fact/truth about their beloved religion, so I going to post a few links explaining my statements.

Again - I was NOT trying to start a flamewar, as I like .NET - I just call it what it started as: A TOTAL RIP-OFF FROM JAVA (there I said it, flame me!)

As Microsoft couldnt push JAVA in their own prefered direction, they decided to "invent" .NET and decided NOT to include Java-VM any longer. Harming SUN's distribution and forcing customers to choose .NET or manually downloaded JAVA

Microsoft lost to SUN

http://itmanagement.earthweb.com/entdev/article.php/1561231/Sun-Wins-Injunction-Against-Microsoft-in-Java-Case.htm

Compare JAVA vs C# which could be developed without the flaws learned from the mother language

http://en.wikipedia.org/wiki/Comparison_of_Java_and_C_Sharp

Again, I love .NET and C# for how easy things has gone, what I cant stand is the fact that people try to "hide" the truth of its origins. Give it some credits, thats all - and lets go build some awesome software shall we?

Btw. Android OS (from Google) is build on JAVA as its OPEN... so perhaps we should consider having a second look at that "oooh sooo old and mean JAVA" ???

I dont have a language/code religion... I choose the best tool for the task.

BerggreenDK
-1: I think you should provide some references. I believe your timing is off, at the very least.
John Saunders
References to what? the languages equality or links to the news about Microsoft loosing to SUN?
BerggreenDK
http://msdn.microsoft.com/en-us/library/ms836794.aspx#tchwhatssimilarbetweencjava
BerggreenDK
Dude, I think you don't understand your history very well. Java and C# have a shared parent: C/C++; which is why their syntax is extremely similar. For .Net, Microsoft hired key people (including Anders Hejlsberg) from Borland who had created Delphi.. Which the .Net core is actually closer to than it is Java. If there was any one person responsible for .Net it's this guy: http://en.wikipedia.org/wiki/Anders_Hejlsberg
Chris Lively
No, you are not right Chris as I see it. C/C++ are compiled languages that produce assembler/machinecode. Java and C# or rather any .NET language is compiled to "CLR code", which is similar to the byte-code Java produces. This makes it transparent to CPU architecture and allows it to run in a managed-virtual-machine. Hench, Java was the first language to use this and as my previous link (this one: http://msdn.microsoft.com/en-us/library/ms836794.aspx#tchwhatssimilarbetweencjava) shows, that EVEN Microsoft compares the languages.
BerggreenDK
Btw. just to mention a few more of the similarities: Type-Safe Language, "Pure" Object-Oriented Language, Built-in Thread and Synchronization Support, Built-in Unicode Support, Garbage Collection and loads of other benefits by running in a virtual machine. C/C++ handles "objects" by using memory pointers just as an example. Please stop voting me down on this. I like all the languages, I am just trying to prove my point here!
BerggreenDK
@Berggreen you are being voted down because you are wrong Java and .NET have the shared parent of C/C++. Your last comment shows you aren't understanding. Type safety, OO, thread sync and unicode support have nothing to do with the virtual machine lots of languages have these. Also byte code is just a refined type of interpreted language Java wasn't the first to do it.
PeteT
@BerggreenDK: "Java was the first language to use this" neither the concept of bytecode nor the concept of garbage collection was pioneered by Java. The concept of bytecode has been used in a few languages including UCSD Pascal and more recently original Visual Basic p-code. Garbage collection was used in various languages including the Lisps and Smalltalk.
Muhammad Alkarouri
@PeteT can we agree upon that .NET was very much influenced by JAVA and then Microsoft added a lot of extra good stuff? My point is that Microsoft realised that JAVA's virtual machine architecture was a very smart approach and as they couldnt control the development, they decided to build a new "cup of coffee" with all the previous faults fixed from start + adding all their own visions? I dont hate Microsoft nor .NET
BerggreenDK
@Muhammad Alkarouri - I am sure you know what you are talking about, might have been too specific there. My fault. But - my point is that Microsoft STOLE/LEARNED/GOT INSPIRED (pick what you want) their own platform from what they learned from the JAVA experience. Not the others you mention.
BerggreenDK
@BerggreenDK: What you are missing is the huge influence of others, in particular Delphi. Chris already mentioned Hejlsberg, the architect of both Delphi and C#. Comparing C# 1.0 with Delphi and Java, you will find the influence of Delphi to be bigger. With the exception of the virtual machine, which is similar to Java's but is not specific to C#. Nobody suggests that VB.Net is a copy/inspiration of Java, for example.
Muhammad Alkarouri
@Muhammad @PeteT and the rest of you guys. Stop, please. Read what I wrote. I said the ".NET" idea is a ripoff from JAVA. Ofcause every language is influenced by another. But its just very "interesting" how .NET suddently was "invented" by Microsoft after they lost their case to SUN. Thats what I've being saying ALL the time. And C# is designed/invented by Anders yes, but WHEN was he hired by Microsoft? Before or after the JAVA/SUN insidence? Think about it again. If I wanted to build a new language I would hire an expert too and tell him to "have a look - this is what we want, but better".
BerggreenDK
@Muhammad Microsoft had to make it possible to move there large VB-developer database from old compiled to "EXE files" and if they wanted those to be able to use .NET (not having to learn C#) there had to be a VB.net - again. .NET is running on a VIRTUAL MACHINE. Thats my point. Microsoft learned this was the future from their work with the JAVA VM. I dont say they made a rough "copy", they just got VERY inspired to say the least. And thats been my argument from the start. They wanted to build a "better cup of JAVA", but couldnt use the name.
BerggreenDK
@BerggreenDK: We know that you are saying that .Net is a ripoff from Java. Probably you weren't following the details then. You probably know that the Microsoft/Sun suit was about J++ (Microsoft changes to Java) which were developed by Hejlsberg in Microsoft. So he was hired before the suit. Was .Net influenced by this? Certainly. Did Hejlsberg have the idea to do something Java based since his Borland days? May be. Was Delphi a big influence? There is a reason the .Net library is more similar to the Delphi VCL than to Java AWT/Spring. Where did C# get properties, events and indexes from?
Muhammad Alkarouri
@BerggreenDK: By the way, reading all the comments I think you are mistaken about "Microsoft evangelism". You didn't get your history right. In the 90s the company that was the Microsoft "nemesis" in development tools (so to speak) was Borland. Microsoft effectively dismantled Borland by taking a lot of their programmers finishing with Hejlsberg (a suit followed and was settled). What you managed to do is rewrite history to remove Borland and Delphi off the map. To give you a feeling with the situation then I leave you with this http://delphi.about.com/od/delphifornet/a/conspiracydnet_2.htm
Muhammad Alkarouri