Linked by Thom Holwerda on Tue 4th Sep 2012 20:04 UTC, submitted by MOS6510
General Development "Computer programming is the art, craft and science of writing programs which define how computers operate. This book will teach you how to write computer programs using a programming language designed by Google named Go." Freely available book on Go.
Thread beginning with comment 533935
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Ugh
by Lobotomik on Wed 5th Sep 2012 11:48 UTC in reply to "Ugh"
Lobotomik
Member since:
2006-01-03

Well, it looks like quite a large community of Python programmers totally disagree. But you must know better...

Reply Parent Score: 4

RE[2]: Ugh
by Slambert666 on Wed 5th Sep 2012 14:00 in reply to "RE: Ugh"
Slambert666 Member since:
2008-10-30

Well, it looks like quite a large community of Python programmers totally disagree. But you must know better...


Well, did you know that the most, by far, requested change to the python language is to allow it to use curlybraces instead of indentation.

Python3 also tries to fix some of the puke in Python2 so now there are two incompatible versions of Python.

Reply Parent Score: 1

Cite?
by sgtrock on Wed 5th Sep 2012 18:33 in reply to "RE[2]: Ugh"
sgtrock Member since:
2011-05-13

Show me the bug report. Show me the continual discussions by all and sundry involved in development and use of Python. It doesn't exist.

The truth is, people who program in Python quickly learn the same lesson http://www.linuxjournal.com/article/3882>

<blockquote> Of course, this brought me face to face once again with Python's pons asinorum, the significance of whitespace. This time, however, I charged ahead and roughed out some code for a handful of sample GUI elements. Oddly enough, Python's use of whitespace stopped feeling unnatural after about twenty minutes. I just indented code, pretty much as I would have done in a C program anyway, and it worked.

That was my first surprise. My second came a couple of hours into the project, when I noticed (allowing for pauses needed to look up new features in Programming Python) I was generating working code nearly as fast as I could type. When I realized this, I was quite startled. An important measure of effort in coding is the frequency with which you write something that doesn't actually match your mental representation of the problem, and have to backtrack on realizing that what you just typed won't actually tell the language to do what you're thinking. An important measure of good language design is how rapidly the percentage of missteps of this kind falls as you gain experience with the language.

When you're writing working code nearly as fast as you can type and your misstep rate is near zero, it generally means you've achieved mastery of the language. But that didn't make sense, because it was still day one and I was regularly pausing to look up new language and library features! </blockquote>

IOW, it's not the whitespace that's the issue, it's your refusal to recognize that you're indenting anyway. You're giving up on a language long before you give it a chance for the wrong reason. :-)

Reply Parent Score: 3