A word of caution, this is a rant

At work I use Windows, that's how sad my life is. I *do* believe many of the windows bashers are either Mac or Linux fanboys that just rant for the troll factor, and the fact is that they have never used windows for "real" work (or have a very limited experience using it besides playing games).

On the other hand, I like to think of myself of someone that is used both platforms for development "real world" applications, As a little background, here's my programming history in a nutshell: During the Windows 3.1/95/98 era, I worked with image, ocr and transmission systems, developing mostly in VB, (Visual)FoxPro and the like, then, during the next 10 years I used Linux exclusively for all my work (change jobs, dot com boom et al), then moved onto the OS X platform for 3 years (Which I still love) and now I am back to Windows at my current employer.

I am working on this middle-tier, back-end application which generates several custom COM+ components for use on a rather large CRM system, my code requires to integrate seamlessly with the CMR system's VB DLLs and implement a set of business rules that the company enforces, all fun stuff (in the honest sense). The application is written in C#.

Because of several (believe me, many) constraints, developing in our local PC has proven to be a real challenge, to put it some way, impossible would be more accurate, since the Custom COM+ component interacts directly with the CRM software, no proxying is allowed, MS Devs would know what I am talking about.. so, to make the story short, I have to develop in the development "server".

This creates a big problem: Windows Terminal Services (2003) allows for only 2 remote connections (plus the monitor), which means that while I am developing in the development server, only one more user can interact with the server, and since our app devs count is far greater than that, I am usually "forced" to stop working in my project and wait for other users to run or test whatever is that they run or test.

By "maximum number", you mean 2, right?

How come on earth a quadzillion-CPU, petaflop-ram-rigged piece of hardware cannot accept 5, 10, heck, 100 simultaneous connections??? - well, you see, when you RDP in the server, the bandwidth consumed is enough to botch the connection down to its knees, now, connect another user, then another and there you have it.

As I put it to one of my fellow developers when he asked me to "clear my connection to the server": "..This windows limitation nonsense crap of RDP connectivity is another reason why Windows is such a poor OS.."

In Linux, all you need is a ssh session and the world is yours, 50 concurrent connections? bring them on, yes!, why can't in windows be like that. This is just sad.