On Mon, Oct 8, 2018 at 11:24 PM Zoom.Quiet <[email protected]> wrote:
>> I just took at the Nightlight sources. There are 5 .clj files in src/clj/nightlight directory, and 11 files in the src/cljs/nightlight directory. Most files are less than 100 lines long. The only files larger than 100 lines are: > short not amazing for clj, just the JVM ecology > in fact, nightlight like Ajax, just make up existing software as new feature. Thanks for this. I suspected as much, but I hadn't gotten around to verifying it. > Leo is the only creator for literature programming in Python ecology, so had to build everything need. One of my biggest mistakes has been not using existing tools. Yes, Leo's "ecology" sometimes makes using those tools problematic, but that's not a convincing excuse. For example, it's likely that using pygments <http://pygments.org/>would have simplified Leo's syntax coloring. And Leo has only recently supported jedi <https://jedi.readthedocs.io/en/latest/>auto-completion (there are still some bugs). Imo, the core of the dream is to have better inter-process communication, As you said in another reply in this thread, at present Leo is like a huge kernel. Instead, we would like to have an unchanging fast server that coordinates various components. I'm not sure exactly what this means or how to do it, but it does look like the way forward. Pyzo's yoton <https://iep.readthedocs.io/en/latest/yoton/>library might be the foundation for this. 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.
