Re: Going from PerlScript on NT to *NiX

I wish you luck, because I fear you'll need it. People who have spent their lives on Windows don't look kindly at a *nix CLI. Have you ever seen someone's first attempt at using vi? I always get out of swinging range when they can't figure out insert/command mode.

On a more serious note, you'll need to see if you are using any MS-specific stuff. Don't want to find out down the road that you *must* have access to a bunch of COM objects not available on the *nix platform.

Comment on Re: Going from PerlScript on NT to *NiX

Replies are listed 'Best First'.
Re: Re: Going from PerlScript on NT to *NiX by Anonymous Monk on Jul 13, 2001 at 17:45 UTC
Why CLI? Even vi has a GUI (so I hear)... so does Emacs. And Komodo runs under Linux, giving you Perl & Python in a GUI. As for porting from VB, there once was something out there to interpret VB, but it was pretty poor... I thought I got it from CPAN, but I don't see it there any more. `Inline::VBASIC` or something similar. Plus, there's the option of "staging" the transition. Teach Perl, leave the Win32 box up, gradually move things over as they're rewritten. I've worked in (several) shops where the migration from Win32 to Linux was carried out by making rewrites of each module in the schedule... Don't forget about VNC. VNC's Java plugin is an easy way to get access in "GUI mode" to your server (over the LAN, unless you're using SSH and have bandwidth to spare!) from non-Linux workstations. (Linux \|\| Unix \|\| Solaris \|\| Irix, &c. ad nauseum)	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Going from PerlScript on NT to *NiX
by Anonymous Monk on Jul 13, 2001 at 17:45 UTC

Why CLI? Even vi has a GUI (so I hear)... so does Emacs. And Komodo runs under Linux, giving you Perl & Python in a GUI.

As for porting from VB, there once was something out there to interpret VB, but it was pretty poor... I thought I got it from CPAN, but I don't see it there any more. Inline::VBASIC or something similar.

Plus, there's the option of "staging" the transition. Teach Perl, leave the Win32 box up, gradually move things over as they're rewritten. I've worked in (several) shops where the migration from Win32 to Linux was carried out by making rewrites of each module in the schedule...

Don't forget about VNC. VNC's Java plugin is an easy way to get access in "GUI mode" to your server (over the LAN, unless you're using SSH and have bandwidth to spare!) from non-Linux workstations.

(Linux || Unix || Solaris || Irix, &c. ad nauseum)

[reply]
[d/l]