In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Stas Bekman) 
wrote:

> I've just found this nice article by Michael Schwern in Simon Cozen's 
> web log: http://www.oreillynet.com/cs/weblog/view/wlg/461
> 
> Michael is talking about why Perl is good for him, not why 'Java is not...'
> 
> Good advocacy stuff.

Nice article and definitely sums up a lot of the reasons *I* never got 
involved with Java even after buying a Book on it once, long ago, before 
I even looked at Perl. 

This was LONG before I was exposed to the whole OO thing, and the whole 
notion of needing to know all this stuff before you could do a simple 
'hello cruel OO world' kept me from delving into it. By the time I could 
get to the parts where you actually were learning to DO anything, I had 
completely lost interest. (despite several attempts at grokking it)


Perl, on the other hand, despite my initial fears (I'd looked at some 
early *.pl files (obviously now these were Perl 4 constructs, and much 
much messier than what we have now) and was thoroughly mystified at my 
inability to understand what they were doing. Tcl, at the time, was easy 
to follow, and the jump to Perl scared me away back then too) fell into 
place like crazy. I'd found comp.lang.perl.misc, the Programming Perl 
book, and a working copy of Perl for the Mac (MacPerl 5.20r4, which ran 
SO much better and more cleanly than anything else I'd played with thus 
far.. ) and was able to wade right in. All the documentation was there. 
Everything was right at my fingertips. 

Within weeks I was happily hacking away at my ideas that had been 
floating around in my head, and working cross-platform on the unix shell 
at my then-ISP. bliss! :-) ...though I shudder looking back on some of 
that early code :D

-- 
Scott R. Godin            | e-mail : [EMAIL PROTECTED]
Laughing Dragon Services  |    web : http://www.webdragon.net/
It is not necessary to cc: me via e-mail unless you mean to speak off-group.
I read these via nntp.perl.org, so as to get the stuff OUT of my mailbox. :-)

Reply via email to