I *totally* agree with Michal!
He explains more clearly what I meant.
Different platforms require different choices, and real-world setups proved that .NET
is the best choice for the Windows Server platform. It is nicely integrated, very
well supported, and indeed, runtime is the key!
BTW, Michal, I just LOVE the tools you wrote for Server and XMail Administrators!
Tuesday I will implement your DNS Sync and XMail Sync programs on several production
servers. Thank you for sharing your .NET programming skills with the community! I will
do the same with some of the extensions I wrote for XMail, Webmail and
Server/AD/Domain/IIS setup.
Fr�d�ric
----- Original Message -----
From: Michal Altair Valasek
To: [EMAIL PROTECTED]
Sent: Sunday, May 16, 2004 7:00 PM
Subject: [xmail] Re: Xmail reports -- anyone have a wish list?
|And finally, for the $64000 question: Can you explain me WTF
|difference
|does it make for a report tool, that reads text files and spits HTML
|(and that it is absolutely not performance critical), the
|language that it is written in?
It's not important what language uses the given application. Runtime is what
is important.
For typical Windows system administrator, running Perl or Java application
is pain in the ass. The runtimes are complicated to install and setup and
tends to break any given security architecture existing.
In the above situation, installing such runtime is a truly religious
experience: you can't understand it, you must blindly faith in it.
When installing any standard Windows application, I am able to interact with
it. If there are any problems, I can try to solve them. In case of
miscellaneous runtimes such as Java, Perl, Cygwin and so on, all you know
about your system architecture (and as I am Microsoft MVP, it's not too
little in my case) is worthless. You can install it and then it either runs
(and you can simply pray for it to be reliable) or it does not run. In the
second case you generally can't do anything, because it does not interact
the proper way regarding to your operating system.
Situation of .NET framework is different. It's runtime, which is written in
style of being cooperative with Windows OS. It's supported. It's documented
the obvious way. It's incorporated in operating system (in case of Windows
2003 and above) and so on.
Not everybody is prepared to give their vital system as hostage of some
totally strange runtime he knows nothing about.
I have nothing against Perl or any other programming language. There are
systems, where they are at home. Use them there. All attepmts to do
something else are mostly *failing* in production environment.
-- Michal Altair Valasek [EMAIL PROTECTED]
Altair Communications - web hosting, web design, application development
___________________________________________________________________________
http://www.altaircom.net | PGP: 0xC4F3579D | Phone (support): +420602137341
When it's inevitable, relax and enjoy it.
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
