You aren't considering the benefits of custom Python code in adding functionality. I have several Leo-hosted apps I use all the time. To recreate them in LeoJS, I would have to learn how to do equivalent things in ts/js and VS Code. I'm not against learning new things but I've already done that once with PyQt and Python. Now I want to use them, not reinvent them. I'm sure many others are in the same position.
If you are using LeoJs without writing code for it, then sure, it's great! The two code bases are sure to diverge in time. It always happens. On Saturday, July 6, 2024 at 6:32:16 AM UTC-4 Inspired Mars wrote: > (From the other discussion thread that emerged from this one): > Ed wrote: > >Leo isn't an idea, it's a Python program. > > That perfectly summarizes why the new product needs to be its own thing > with its own name and destiny. > There are zero dependencies between it and Leo. > Do you now see how freeing it is to completely separate the two? > > IMHO, the legacy app ought to be retired as soon as possible. > Seems no reason to have two disparate code bases doing the same thing. > In any case new users ought to be spared the cognitive overload of this > (to them) weird clone. > > On Saturday, July 6, 2024 at 4:31:31 PM UTC+7 Edward K. Ream wrote: > >> On Friday, July 5, 2024 at 10:24:42 AM UTC-5 Inspired Mars wrote: >> >> The millions of people that use Visual Studio Code have no idea what >> Leo is. >> >> >> LeoJS will educate them :-) >> >> 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/4dc65047-6ab8-43ee-ab14-a727b2dde4f6n%40googlegroups.com.
