On Wed, 2005-10-12 at 17:27 +0200, Manuel Kasper wrote:
> On 12.10.05 17:17 +0200, Jonathan De Graeve wrote:
> > What about perl?
> > Supports, 00, is not TOO difficult and can be compiled directly to
> > an executable :D
> Why not? I haven't used perl much, and certainly never touched its OO
> features, so I can't comment on its suitability - have you already
> had some experience with it?
> > But I still like to keep PHP since all the work people put into it.
The first scripting language that I learned was PHP. It was very easy
to pick up, but it couldn't do a few things that I wanted it to. I then
started working on Perl. Perl has a much steeper learning curve, but
once you're over that initial slope, it isn't bad at all.
Personally, I feel that PHP is still better for writing web apps, but
Perl is much more suited for backend daemons, cli apps, system
configuration and the like. CPAN is great - there is very seldom
anything in Perl that needs to be written from scratch. Jonathan might
cry if he sees this, but much of the PHP/RADIUS stuff he's done is
probably already done in Perl: http://search.cpan.org - search for
OO in Perl is a little different, but very effective once you get the
hang of it.
Has anyone pondered using SOAP? We could use SOAP::Lite for the Perl
core, and then use PHP5's SOAP Interface on the webGUI. This would give
someone the ability for someone to write a Windows admin app in .NET or
many other possibilities.
Regarding OS of choice, I would probably throw my vote in for FreeBSD 6,
as long as the performance comes up. I feel that the 5.x series was the
red-headed stepchild of FreeBSD - a period of transition. Linux would
be my second vote, with OpenBSD being third.
Setting up a svn repository is the best idea I've heard so far.
Just my $.02,