1 |
Dennis Allison wrote: |
2 |
... |
3 |
> My point was/is that programming is language independent. I've |
4 |
> always liked Michael Griffith's comment about programming: "I always |
5 |
> use the same programming language no matter what the compiler" or |
6 |
> something like that. Using a polymorphic, internally consistent, |
7 |
> object-oriented language like Python is a good framework to learn |
8 |
> programming. I think Python does a pretty good job of capturing the |
9 |
> abstractions you need to write simple, conceptually clear programs. |
10 |
> You don't have to worry about the nits, you can program interactively |
11 |
> and see what happens, and there's not the huge overhead of type |
12 |
> mechanisms to drag into every single little program. The language is |
13 |
> introspective (aka introspective) so programs can learn about their |
14 |
> own structure. |
15 |
|
16 |
i agree 100% - python was the first gerneral purpose scripting language |
17 |
I learned, and has still been by far the best experience. |
18 |
|
19 |
esr sums it up particularly well in his 'why python'[1] post on the |
20 |
linux journal: |
21 |
|
22 |
"My second came a couple of hours into the project, when I noticed |
23 |
(allowing for pauses needed to look up new features in Programming |
24 |
Python) I was generating working code nearly as fast as I could type. |
25 |
When I realized this, I was quite startled. An important measure of |
26 |
effort in coding is the frequency with which you write something that |
27 |
doesn't actually match your mental representation of the problem, and |
28 |
have to backtrack on realizing that what you just typed won't actually |
29 |
tell the language to do what you're thinking. An important measure of |
30 |
good language design is how rapidly the percentage of missteps of this |
31 |
kind falls as you gain experience with the language." |
32 |
|
33 |
this is from an experienced programmer's point of view, but i think it |
34 |
reflects well on the general experience people have picking up python - |
35 |
once you get past the enforced-whitespace-formatting quirk it becomes |
36 |
very easy to understand what you're doing. |
37 |
|
38 |
1. http://www.linuxjournal.com/article.php?sid=3882 |
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |