Linked by vodoomoth on Fri 24th Sep 2010 22:56 UTC
Thread beginning with comment 442741
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Java = Servers. C# = desktop
by nt_jerkface on Sun 26th Sep 2010 17:51
in reply to "Java = Servers. C# = desktop"
Ergo, Java for servers. C# for desktop. If there where good implementation full support of C# on Enterprise OSes, such as Unixes the servers would also use C#. But as of now, the servers only use Java/C/C++.
Funny how myspace uses asp.net just fine:
http://weblogs.asp.net/scottgu/archive/2006/03/25/Handling-1.5-Bill...
Java on servers is a productivity sink compared to asp.net. Ruby in steel is a better alternative.
RE[2]: Java = Servers. C# = desktop
by dekernel on Mon 27th Sep 2010 02:19
in reply to "RE: Java = Servers. C# = desktop"




Member since:
2010-08-29
In my line of work, the servers are BIG and handle millions of transactions worth billions of dollar, each day.
Those servers are always running Unix/Linux/OpenVMS. They can not run Windows, because Windows becomes unstable at high loads with clustered solutions.
On Unix/Linux/OpenVMS servers we find good implementations of Java. There are no good implementations of C# nor .NET. Mono is not an option, when you handle billions of dollars each day - you need full 24/7 support from MS.
Therefore all BIG servers are running Java/C/C++. On the desktops who runs Windows, we see C#.
Ergo, Java for servers. C# for desktop. If there where good implementation full support of C# on Enterprise OSes, such as Unixes the servers would also use C#. But as of now, the servers only use Java/C/C++.