Re: Website Development

Zackary Deems <[email protected]> Sun, 07 Sep 2003 16:39:01 -0400
Newsgroups gmane.linux.arklinux.webdevelopment
Message-ID <[email protected]>
Thanks for letting us know ahead of time, Amoeba.  We're more than happy 
to work with you on your schedule, as we know regular jobs, family, and 
life in general keep people busy.

The decision to use perl was based on a number of factors, not the least 
of which is the fact that neither boris nor myself speak php, and both 
of us have successfully built highly functional, professional websites 
using 100% perl.  The other reason is because perl IS the more powerful 
and flexible of the two, between PHP and perl. 

In my experience, perl is only hard to follow in cases where coders take 
lots of shortcuts, fail to document code, and where they use 
unnecessarily complex methods of accomplishing things.  If the concern 
is that anything we develop will be hard to follow for newbies, then one 
of our requirements can be to document everything, and choose easier to 
read methods of accomplishing things, unless doing so would compromise  
performance.

However, until such time as we see a 'regular' developer base step 
forward, it would be very difficult for us as a team to agree to do 
development using tools unfamiliar to those of us who would be left to 
'fix' things if the original coder is nowhere to be found.

For the time being we're choosing experience over simplicity. 

Tuesday night, one of our topics for discussion will be the proposed 
site layout and design.  If you have input for this discussion but 
cannot attend the meeting, please put your ideas forward to this mailing 
list now. 


Cirnath


Robert Smith wrote:

>I would first of all like to appologise for not making the meeting. I was busy at work during the meeting time and so could not make it.
>
>I will not be able to make the meeting on tuesday as I am away on business again.
>
>I will be there next sunday to take part in the meeting.
>
>Secondly I would like to object to the usage of perl as a backend, unless it is integrated into the main web pages e.g. ASP style perl. This is because it is more difficult to follow when programming IMO. I also do not believe that perl is web specific enough, and although it would be a benefit for some parts to be perl coded, i think that it is too confusing for a> beginners wishing to take part and b> easy collaboration due to the hundreds of ways of doing one thing.
>
> I would recommend PHP, but a lot of people do not like it. Perhaps a PHP/PERL/PYTHON web backend could work?
>
>Amoeba
>
>
>
>  
>