Well said. +1.
On Saturday, May 7, 2016 at 1:49:16 AM UTC-7, DNF wrote: > > I find 'end' to be the best choice of block terminator among the ones I > have seen. > > It is very clear and explicit, there is no doubt as to what it means, > unlike '}' which is way too small and ambiguous (does it mean end of block, > or end of dict definition, etc.), and just does not jump out at you the way > it should. > > You are also wrong that it takes longer to read, since you read it as a > single unit, you don't parse every single letter, unless you are in the > process of learning to read. And since it is so unambiguous, it is much > faster to read than any alternative I've seen. > > As for whitespace-dependent, Python style, block delimiters, I have been > working with those over the last few months, and have learned to abhor > them. They are very brittle, outdent something by accident and the code > breaks, perhaps completely invisibly. If you share code with someone that > uses 2-space indentations (as I have), fixing that is a big headache. Last, > but not least, it completely lacks the tidy symmetry and definitiveness of > begin-end blocks, the code seems to slide across the page and then just > trail off like a bad idea abandoned in mid-thought. > > I love 'end', please keep it :) > > On Friday, May 6, 2016 at 8:26:15 PM UTC+2, Ford Ox wrote: >> >> Is there any reasoning behind it? It seems to me like a weird choice >> since you have to type three letters, which is the complete opposite of the >> goal of this language - being very productive (a lot work done with little >> code). >> On top of that, brain has to read the word every time your eyes look at >> it so you spend more time also reading the code - tho this should be easy >> to omit, by highlighting this keyword by other color than other keywords >> (the current purple color in ATOM just drives me crazy, since it is one of >> the most violent colors, so my eyes always try to read that useless piece >> of information first, instead of the important code). >> >
