I actually do think it would be a really good thing to have a statfinder
within sage, and somehow merge findstat code with sage code. It would
benefit both sage and findstat users. At the end, both FindStat and Sage
have the same aim: using computers to help us doing research. I understand
completely that it should have no impact on performance for other people
(but it is true for every code someone adds...) but I do not understand the
"it is useful only for FindStat users so it is not useful". Anyway, this
not going to happen in the near future, I mostly see this as long term
objective and it is only my opinion.

The short term perspectives is for "us FindStat people" to build a FindStat
API that would allow query from external websites. It does not seem that
complicated, it's mostly a question of taking the time to do it. Once we
have that, we can start thinking of more integration, local computation,
etc.


2014-05-29 22:35 GMT+02:00 John Cremona <john.crem...@gmail.com>:

> On 29 May 2014 21:02, Nathann Cohen <nathann.co...@gmail.com> wrote:
> >> > BUT: this would result in code in Sage that is not useful purely
> >> > within Sage. And there are people, loud people, that say there should
> >> > not be such code in Sage.
>
> I do not know what is "code in Sage that is not useful purely within Sage".
>
> John
>
> >>
> >> I can hear your frustration ... In similar situations, it helped me to
> >> keep in mind that loud people are not always representative. Of course
> >> the difficulty is to fetch the opinion from the others.
> >
> >
> > Ahahahahahahah. Well, only including in Sage code that is useful to "a
> Sage
> > user" or "other developpers" does not seem that far-fetched. I still do
> not
> > see what the problem is with that.
> >
> > Err.... Well, assuming the obvious : that I am the "loud people" you
> > mention.
> >
> > Nathann
> >
> > --
> > 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 post to this group, send email to sage-devel@googlegroups.com.
> > Visit this group at http://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to