in message <[email hidden]>, Tim
Woodall (') said:On Thu, 07 Apr 2005 08:03:18 +0100,
Keith Willoughby said:Not Responding said:My question is, where do I start? I'm so out of date I can't even
ask the right questions. I used to write in Pascal, C, C++ and,
once, Visual Basic. That was all mainly under DOS (or for embedded
systems). What do I want to do? I'd like to be able to tinker with
databases, use the Windows GUI with ease and pull stuff off the
internet to manipulate.
Any ideas?
Python, Perl, or (my choice, but it's not exactly mainstream) Ruby.
Ruby is, IMO, the most elegant of the three, and Perl the ugliest,
but Perl has a better range of libraries.
Nobody has mentioned Lisp yet. It's on my must learn list but i'm
short of round tuits ATM.
Ah, LISP.
What can I say? It was my first language, and I loved it. I still think
it's the best and most powerful programming language. I served on the
BSI committee on the standardisation of LISP as we fought the rearguard
action against Common LISP. Common LISP is a horrible abortion -
FORTRAN with brackets - and has really killed the whole LISP thing.
If you want to play with LISP, play with Scheme. No, Scheme isn't really
LISP; lexical closures may be elegant and efficient but they don't have
the expressive power of deep binding. But Common LISP has separate
namespaces for data and functions, and is very badly adapted for
in-core develoment (the basic unit of compilation is the /file/, for
heaven's sake. What place has /file/ got in a LISP world?) so it isn't
really LISP at all. It's just a sad, ugly, sorry, mess.
This isn't to say that earlier LISPs don't have problems. They do. The
chief of these are the issue of binding and its consequences for the
semantics of interpreted and compiled code, and the issue, in big
systems, of namespace collisions. But all the hardware issues that made
big LISP systems problematic have largely been solved by cheaper
hardware, and to have (for example) InterLISP-D on modern hardware
would be an awesome development environment. OK, yes, InterLISP is also
a LISP2, but it is optimised for in-core development and the structure
editor (DEDIT) was just so much nicer than any other code editor I've
ever used.
--
[email hidden] (Simon Brooke) http://www.jasmine.org.uk/~simon/
"The result is a language that... not even its mother could
love. Like the camel, Common Lisp is a horse designed by
committee. Camels do have their uses."
;; Scott Fahlman, 7 March 1995