Accessing the server remotely!
A kind of Slashdot post; but it’s interesting
I happened to meet a developer today; he is from Karachi; and has come to Lahore on a project that we are doing for a client. (He is client representative as well). We had to decide the platform today for the client; the base product we are using happens to support both sides of the world, Windows and UNIX. He argued that “Unix is better; as it’s easier to access remotely.” I didn’t want to have any long discussions; as I had to attend another meeting and wanted to leave quickly </smile> but there are two arguments that came to my mind.
- One was reactionary; that Windows has improved a lot in recent times; Remote Desktop (RDP) is no doubt one of the best things being introduced in Windows. RDP clients are available from desktop machines to phones. (Smartphone) And having graphical interface gives the feeling that we are living in 21st century. (Common Unix guys; you have to eat this; those blinking cursors are past; come up with something nice)
- Second one is; that no doubt there may exists better implementation of “Server products” for Windows; but they don’t get wide acceptance due to the reason that you need to have a “GUI” interface/access to perform administrative work; which many administrators don’t like. Consider for-example Exchange (don’t flame me arguing it not a better “email system”, I am using it for just an example) the administrator needs to logon to some machine; fires up some GUI interface; follow some wizard to create a mailbox.
We as a developer should understand that if we are making some “server” product on Windows; we should expose administrative commands using approaches like WMI, WSH. (Exchange does support many of this) or using a more recent approach, Monad; the next generation shell that will be shipped with Exchange 12. Monad has got some cool stuff that most of the UNIX shells lacks. Having Monod on a telnet session to a Windows will be definitely a better experience than BSH/KSH/BASH of Unix.