Why Python rocks for research
101–103 of 103 posts
Re: Why Python rocks for research
#102Earlier quoted context omitted.
> The 80 chars limit has a justification: expressions that don't fit on 80 chars (or two lines using parens) are not readable anyway I disagree. There are many cases, especially after 2-3 levels of indentation, where 80 characters is an unreasonably narrow space. I don't have a strong preference for reading code within 80 characters. And I'd much rather comments use 80 characters plus indentation rather than worry ab…
> > The 80 chars limit has a justification: expressions that don't fit on 80 chars (or two lines using parens) are not readable anyway > I disagree. There are many cases, especially after 2-3 levels of indentation, where 80 characters is an unreasonably narrow space. Some people would say that after 2-3 levels of indentation you should be looking at refactoring your code. Probably to pull something into a separate fu…
Re: Why Python rocks for research
#103Earlier quoted context omitted.
>Code should not be Documentation. Code is for humans to read, that it compiles/interprets to a program is a side effect. Otherwise we'd all be passing around binaries (or byte encoded files) with our thick stacks of documentation.
What's your take on the multitude of software that you buy together with all the README files, Word or PDF documents describing how to use the software, what does it do, and all that jazz? Do we (humans) get to view all that code and see what Microsoft Office Word 2007 can do for us?
Why do you assume I buy any software?
The claim "code is for humans to read" does not logically lead to claim "code is the only thing for humans to read". There are different kinds of humans, programmers, maintainers, end-users, and idiots are some. You're a member of the later.