NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Smalltalk etc (Score:1)
I have actually been paid to program in SmallTalk twice, and to build an interface from one Scheme to another with C. I went from C to SmallTalk to Objective-C to C++ to Perl (and Java), so perhaps I can provide some perspective. I have coded just about every "write only language" -- most of them for pay.
Apart from Simula and the like, Smalltalk is the purest OO language
Bill
# I had a sig when sigs were cool
use Sig;
Re:Smalltalk etc (Score:1)
One reason is badly dated mis-information like this!
"Historically, lack of integration with legacy databases"
Pre-historically! Smalltalk ORM was common from '90
"actively hostile to multiple programmers and source control"
From the late '80s Envy/Developer provided fine-grained (method level versioning) source code management. All the code was in a multi-user, replicated, database.
"Wall Street had... Patching live code on the fly is scary"
Many of those systems a
Show me the money (Ugh!) (Score:2)
I think Envy/Developer is another reason why SmallTalk has issues with acceptance. As a programmer, there are certain things I look for in a development environment, not just a language. I want to know about the language(s) I'll be using, how source control is managed, the database (if any), the test suite, the IDE (if any), etc. I like to learn about those things one piece at a time. Throw too many at me at once, or tell me I cannot use tools that I am comfortable with and I'll likely be less intereste
Re:Show me the money (Ugh!) (Score:1)
Once in a while leave the comfort zone
"but I have to put food on the table"
You and me both.
Reply to This
Parent