On Mon, 7 Oct 2024 at 06:05, Kwankyu Lee <ekwan...@gmail.com> wrote: > > On Monday, October 7, 2024 at 12:24:04 AM UTC+9 marc....@gmail.com wrote: > > > I would say that the motivation is to make it possible for a developer to > > include a self-contained portion of sage in a separate project without > > having to make that project as large as a full Sage distribution. > > OK. That is perhaps a major case that one needs a portion of the sage > library. I can also imagine a user installing a smaller sage library just > because it is enough for him/her.
I suspect that if Sage was modularised then over time people would work on making some parts more portable so that some subset of Sage would be natively installable in WASM or on Windows etc. Greater portability would make Sage more attractive for use as a software dependency. There would also be a strong incentive to try to carve out a meaningful subset of Sage for end-users that was more portable but I don't know how realistic it could be to achieve that. -- Oscar -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAHVvXxTu5rD%3DSJCvEJQPupA%2Bc2sxS79AEjNdkkoXOUOwfodzzw%40mail.gmail.com.
