On Tue, Oct 27, 2015 at 7:59 AM, john lunzer <[email protected]> wrote:
> This is a good summary of Leo's history and capabilities. Because this > thread has been met with some... criticism I will provide my reaction and > some guidance for further posting. > Thanks for your comments. They are spot on. > There are countless features and capabilities I would like to see built into Leo, but alas I don't have a magic code genie to grant me programming wishes. The best way to learn anything is to jump in and do something that interests you. Imo, time itself is hardly ever the real issue: it's energy and confidence. My first python project was the c2py script. It's in scripts.leo. I still remember the dawning realizations that: - One line of python (string-oriented) code would require dozens or hundreds of lines of C code. - Python is infinitely safer than C code. Goodbye the ever-present fear of inserting a really hard-to-find storage allocation time bomb in C code. More details here <http://leoeditor.com/appendices.html#why-i-like-python>. Imo, nobody could grok these advantages by reading documentation or reviews. I just had to immerse myself in the new language. Probably the same is true about Leo programming. HTH. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
