In article <[EMAIL PROTECTED]>,
Ant <[EMAIL PROTECTED]> wrote:
>
>So far? After a bit of pain getting started and finding decent docs
>(while waiting for the books to arrive) I've found the language quite
>easy to use. I haven't got into closures or macros yet - I need to get
>more familiar with th
Hi all,
On Dec 28 2006, 4:51 pm, "Paddy3118" <[EMAIL PROTECTED]> wrote:
> This month there was/is a 1000+ long thread called:
> "merits of Lisp vs Python"
> In comp.lang.lisp.
>
> If you followed even parts of the thread, AND previously
> used only one of the languages AND (and this is the
> cruc
In message <[EMAIL PROTECTED]>, Paul
Hummer wrote:
> I learned PHP for ease of web application development ...
PHP is great for easily developing _insecure_ web applications. But if you
want them not to leak like a sieve, things get a bit more complicated.
--
http://mail.python.org/mailman/listi
In message <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> [3] I thought it was particularly cool how Tcl could bolt on a class
> based object oriented system as a library. The word "class" isn't
> built into the language, but that kind of evaluator lets you add it.
I have written about two notr
Paddy3118 wrote:
> This month there was/is a 1000+ long thread called:
> "merits of Lisp vs Python"
> In comp.lang.lisp.
>
> If you followed even parts of the thread, AND previously
> used only one of the languages AND (and this is the
> crucial bit), were persuaded to have a more positive view
>
Steven Haflich wrote:
> Ray wrote:
> > Can one really survive knowing just
> > one language these days, anyway?
>
> いいえ！ 違います。
iie! chigaimas.
No, I beg to differ!
(Hey, I'm in right the middle of preparing my Kanji-drilling Lisp
program for distribution).
--
http://mail.python.org/mailman/lis
Ray wrote:
> Can one really survive knowing just
> one language these days, anyway?
いいえ！ 違います。
--
http://mail.python.org/mailman/listinfo/python-list
Paddy wrote:
> Carl Banks wrote:
> > If you were so keen on avoiding a flame war, the first thing you should
> > have done is to not cross-post this.
>
> I want to cover Pythonistas looking at Lisp and Lispers looking at
> Python because of the thread. The cross posting is not as flame bait.
Then
Paddy wrote:
> Carl Banks wrote:
> > If you were so keen on avoiding a flame war, the first thing you should
> > have done is to not cross-post this.
>
> I want to cover Pythonistas looking at Lisp and Lispers looking at
That's already covered in the orginal thread. Same two newsgroups, same
crowd
[x-post removed]
In article <[EMAIL PROTECTED]>,
Paddy <[EMAIL PROTECTED]> wrote:
>Carl Banks wrote:
>>
>> If you were so keen on avoiding a flame war, the first thing you should
>> have done is to not cross-post this.
>
>I want to cover Pythonistas looking at Lisp and Lispers looking at
>Python b
Carl Banks wrote:
> If you were so keen on avoiding a flame war, the first thing you should
> have done is to not cross-post this.
I want to cover Pythonistas looking at Lisp and Lispers looking at
Python because of the thread. The cross posting is not as flame bait.
- Paddy.
--
http://mail.py
Paddy3118 wrote:
> This month there was/is a 1000+ long thread called:
> "merits of Lisp vs Python"
> In comp.lang.lisp.
>
> If you followed even parts of the thread, AND previously
> used only one of the languages AND (and this is the
> crucial bit), were persuaded to have a more positive view
>
I am rather annoyed at the "apples vs. oranges" arguments I frequently
see on Reddit and the like. I picked up python last summer after going
through a very messy breakup (it seemed like a good thing to do with all
the alone time). Anyway, ever since I started writing python, I've been
bugged by
Paddy3118 wrote:
> This month there was/is a 1000+ long thread called:
> "merits of Lisp vs Python"
> In comp.lang.lisp.
> (I suspect this thread to be very short - even the
> original poster seems to have given up on the day he
> started the thread).
I use both. And Java, and C++ too. Can on
14 matches
Mail list logo
