On Wed, Jun 19, 2013 at 1:59 PM, David McNab <[email protected]> wrote:
> The rules need to be updated to include Rule 34j, which states "There is a > client-side javascript version of it". In other words, for all software, > there is a corresponding javascript program that is rapidly evolving to > achieve the same thing. > Haha! > > Terry, what you're doing is brilliant and long overdue. > I agree. Thanks for your work. > The whole computing world is headed into the cloud, and if Leo is to stay > relevant, it needs to go there as well. > I have mixed thoughts about this. If we could magically make Leo work in the cloud, then that would be great. However, I don't want to maintain two code bases, one in js and one in python. And nobody else will want to maintain two code bases either. Also, I think of Leo as a python-based editor. A js (or coffee-script) based editor would be something different, imo. There are several python-in-javascript projects (just google "python in javascript"), but iirc according to Guido all are in trouble. I suspect that python in javascript may be one of those ideas that sound good but are actually doomed. There is a term for such things, but I forget what it is. These are my present thoughts, but I don't want to discourage Terry's work in any way! Let's see what happens... 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/groups/opt_out.
