News for hackers. Stuff that matters.
Re:Dear Python by codexon on Tuesday February 02, 2010 @08:52PM (#1096834)
The first index is 0, the next is 1, and if you loop around backwards, it's -1.

Makes sense to me.

Re:Dear Python by jamesbritt on Wednesday February 03, 2010 @01:11AM (#1097191)
"Makes sense to me."

Me too.

But: when I see code that refers to first and last, I expect that the first and last elements are special.

When I see integers, it leads me to think that all of the elements are about equally important.

I also find it easier to read the text form rather than the integers; I don't have to look carefully to see if it's 1, 11, 7; code reading goes more smoothly.

Having both forms allows me to express, and parse, intention better.

Re:Dear Python by stcredzero on Tuesday February 02, 2010 @09:13PM (#1096866)
That's another demonstration of my point. Many, many people out there in the non-tech world would expect that the first element would have an index of "1". First = "1st" = "#1." On the other hand, we often experience the convenience of pointer arithmetic (or similar) with zero-indexed arrays.

Yet another programmer/techy and ordinary person divide.

Re:Dear Python by codexon on Tuesday February 02, 2010 @09:29PM (#1096902)
If you want something for non-techies, you pick something like Applescript.

0-based indexing is noob friendly because most cs algorithms use it so you can do a straightforward translation. Would it be better to go with 1-based and make this harder for novice programmers? I don't think so.