On Sunday 16 May 2004 07:00 am, Michal Altair Valasek wrote: > |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.
So far, so good. > > 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. WHAT? Have you installed Perl on Windows from ActiveState (http://activestate.com)? What is so hard about that? Three or four screens with a few simple options. Are you upset because it wants to install in c:\Perl and not in your magic c:\Program Files? WELL, CHANGE IT TO c:\Program Files by hitting the browse button right there on the screen. I just don't understand your problem. And the 'security issues' - what are you refering to? I can write insecure .Net apps as well as secure Perl apps on windows. I don't think security issues are tied to perl. If your up to it, please give examples of security problems caused by Perl. > > In the above situation, installing such runtime is a truly religious > experience: you can't understand it, you must blindly faith in it. I would recommend going to church for religious experiences. Is this remark prompted by your lack of abliity or ignorance or both? > > 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. Whose 'proper way'? It simply installs the software. What more do you want? You run perl from the command line. Do you know about that? It's really easy. Maybe you should look at my howto on setting up the Windows command line at: http://beaucox.com/mini-HOWTOs/win32-setup-mini-HOWTO.htm#command_prompt_009 > > 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. Do you think the whole world uses Windows? Are you unwilling to learn anything else? I'm not talking about becoming a UNIX expert, just widen you view to accept the fact that not all software is created by MicroSoft and it's minions. > > Not everybody is prepared to give their vital system as hostage of some > totally strange runtime he knows nothing about. Sit down for a day and look at Perl. It works. It's easy to use. It saves time - especially when writing text mannipulation programs. If you feel like a 'hostage', it's your own fault. > > 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. It sure sounds like you have everthing against Perl. Perl works fine in Windows. I have been happily using it on that platform for over five years. Maybe your problem is that Saint Bill has not waved his magic twanger over perl and had his marketing department think up a new name for it - how's "MS .Perl Enterprise/2004" ? Of course, he would have to 'close' the source and charge $1,595 US per copy with site licenses starting at $15,000 US. > > -- Michal Altair Valasek [EMAIL PROTECTED] Aloha => Beau; - 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]
