I also liked the idea of a short program written in each language, all
doing the same thing, as a point of comparison.

 On Fri, 22 Nov 2002
14:41:27+1300 Paul<[EMAIL PROTECTED]> wrote:

> I don't think we should teach users how to program , that would take
> to long, maybe have a special learn-Python-or-Perl-or-Bash for an
> afternoon sometime but learning a language is time consuming and I
> would think that people learn at different speeds and there are heaps
> of tutorials on the net. 
> 
> I agree with Nick Rout, 20 mins may be better than 5 and a summery of
> the rest would be good. I could probably talk for 1/2 hour (maybe
> more) on Python but I would bore anyone who hasn't ever programmed
> before.
> 
> I propose that 10 - 15 mins is spend on the overview of the languages
> eg. for Python - modules available, functionality, 3rd party modules,
> documentation, speed, ease of use, portability etc. and 5 -10 mins on
> the technical aspects such as OOP, JPython, syntax, extensions, aimed
> at those who already know a programming language, but not to long so
> that newbies get bored.
> 
> On Friday 22 November 2002 09:42 am, Paul wrote:
> > Hi,
> >
> > I have an idea for a CLUG meeting. I would be a great help to people
> > who have just started linux to get an brief overview of the
> > different scripting languages, the advantages and disadvantages. I
> > would be more than happy to talk on python. Maybe others could talk
> > on Shell Scripting, Perl, Ruby, Awk, Tcl/Tk and any others.
> >
> > When I started Linux I had to do quite a bit of research till I
> > decided to learn perl, then I decided that it was was probably about
> > as easy to decrypt DES (in your head) than to read a lot of the perl
> > scripts I found on the net. I then learnt python.
> >
> > Just an idea,
> >
> > -Paul
> 
> 

Reply via email to