On Wed, Mar 22, 2017 at 9:58 AM, Kent Tenney <[email protected]> wrote:
Leo is great at managing complexity, some would consider it's strength a > weakness. > > Per a piece I read, the author didn't use an IDE because it made it too > easy to write complex code. A rule of thumb says it's x number of times > harder > to debug than to write (10 times?) so, if you are writing code too near > your limit > of comprehension, you won't be able to debug it. A simple editor demands > that > files and elements within a file be relatively small and simple: easier to > understand > and debug. > This argument is rubbish. You may have noticed that not everything on the internet makes sense. I do however think Leo tends to be complicit in creating 'proprietary' > source code files, > which are too big and complex to be handled effectively outside of Leo. > DANGER! > Large files have advantages as well. If you don't like them, don't create them. To the first approximation, this affects packaging issues only. Comprehension is pretty much separate. As convenient as I find the parsed view of a .py file Leo offers, a unified > view > provides a view of the forest not possible by examining trees: hence no > sentinels, > <alt-x> vim-edit-file. > The various demos recently have convinced me that a unified view is worth having. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
