I feel very lucky to have serendipitously chosen this month to peek back in at Leo and see what's happening! I echo Offray's comment that even though Leo occupies a smaller portion of my activity these days it's imprint on my mind and perception is permanent and abiding. Thank you Edward for all the work you've done and shared with us. You're willingness to think out loud and share your process of working through things in public via the mailng list at least as valuable as the code and application themselves to me. I count you and the Leo community among my mentors.
-matt On Friday, September 16, 2022 at 9:18:43 a.m. UTC-7 [email protected] wrote: > I join to Thomas' thanks. As I said, Leo and this community has been an > important source of inspiration and I'm happy to be part of it since near > 2005 and despite not being much active now that I use other languages > (Pharo, Lua, Nim) Leo's mark continue in my way of thinking documents and > computing metasystems. > > Offray > On 14/09/22 7:34, Thomas Passin wrote: > > It sounds like retiring all over again. There are a lot of folks who are > very happy that you've stuck to it those 30 years! Thank you. > > On Wednesday, September 14, 2022 at 6:51:43 AM UTC-4 Edward K. Ream wrote: > >> At 5 am this morning, I declared the last Leo issue to be complete. I do >> not foresee significant changes to Leo in the future. See below. >> >> Today is an intensely happy/sad moment for me. Leo has been my life for >> well over 30 years. I have no idea what I shall do next. I have >> deliberately put off those considerations until now. >> >> *Why stability matters* >> >> Imo, Leo (the python app) is no longer the leading edge of the Leonine >> world. That honor belongs to leoInteg >> <https://github.com/boltex/leointeg>, a plugin for vs-code, written by >> Félix Malboeuf. leoInteg communicates with Leo using Leo's server, >> leoserver.py. >> >> *Leo's stability doesn't matter much for leoInteg*. Leo's server is >> flexible and could accommodate significant changes to Leo. >> >> However, Félix is now working on leoJS <https://github.com/boltex/leojs>, >> an all-Typescript plugin for vs-code. leoJS promises significant >> performance improvements over leoInteg. There is no need to wait for >> results from leoserver.py! >> >> *Leo's stability matters very much for leoJS*. Félix is transliterating >> (literally line by line) Leo's python code into Typescript. It's a big job, >> but he is already well along. Changing Leo's code base would make >> additional work for Félix. >> >> *Summary* >> >> Today is a milestone for Leo and for me. It's an intensely happy/sad >> moment. >> >> Imo, leoInteg and leoJS are now the leading edges of the Leonine world. >> These two vs-code plugins offer all the advantages of vs-code plus all of >> Leo's unique features. >> >> I want to keep Leo's code stable so that Félix will not have to revise >> his transliterated Typescript code. >> >> 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 view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/177067ab-4706-4d71-ad86-7d7af01655ebn%40googlegroups.com > > <https://groups.google.com/d/msgid/leo-editor/177067ab-4706-4d71-ad86-7d7af01655ebn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/7e51fa31-bd89-4c92-91cf-6ce2d07e3899n%40googlegroups.com.
