On Sep 10, 7:46 pm, William Stein <wst...@gmail.com> wrote: > On Friday, September 10, 2010, Tom Boothby <tomas.boot...@gmail.com> wrote: > >> The examples of slow things I gave are things that should be fast, > >> even in the Sage interpreter. All of these things are fast in Magma > >> for example, which is also an interpreted language, and this is the > >> main reason that Magma is so popular in my research area (and clearly > >> a reason that people would use Magma rather than Sage). > > Why do you think they are fast in Magma but slow in Sage? Obviously I > have my own opinion, but I appreciate hearing yours...
I haven't looked carefully at the code. Probably too much overhead, the code is way too generic or something. For all I know the values are getting converted to decimal strings in there somewhere, it wouldn't be the first time :-) (Or maybe you mean "what aspects of Magma's development history and/or development model led to these operations being fast"? That would be a much longer conversation.) david -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
