On Fri, Jun 20, 2008 at 12:12 PM, parisse
<[EMAIL PROTECTED]> wrote:
>
>> Yes, but the limit algorithm is easy to understand. And Gary is
>> writting the base symbolics, so you don't need some high math to do
>> that.
>>
>
> Then who will write the real stuff?
There are a lot of Sage developers:
http://lite.sagemath.org/development-map.html
[snip -- weird arguments about whose code is harder to build; this has
nothing to do with sage, and I think should not be discussed here.]
> I believe there is a clear distinction between CAS end-users who
> really want binaries with an installer (which I provide for windows,
> mac and linux packages so that they don't have install problems) and
> developers who should have a little bit of Unix background in order to
> solve simple install problems, because their installation might differ
> from install where the source has been compiled before. I will of
> course do my best so that the compilation process works out of the
> box, but I don't think it should be an excuse not to try it further
> and collaborate with the author/maintainer to fix the
> things.
This belief might be why there aren't very many giac developers.
>> > I won't do anything before someone is really interested. It would be a
>> > waste of time, because I don't know python (and learning python to a
>> > fluent level certainly requires some time), I don't know exactly what
>> > to do and I would not have a reasonable insurance that my library
>> > would be integrated in the sage distribution.
>>
>> Yes, that is the real reason (and it's not your fault). But who better
>> should do it if not the one who wrote the C++ code?
>>
>
> That could be done if there was a document somewhere clearly
> explaining how to interact between sage and your library or binary.
> Something like the documentation of texmacs for writing plugins. If
> something like that exists, I would be glad to have a pointer to it.
> Otherwise, I can't do it on my own on a reasonable time schedule.
This is ridiculous with people telling each other to do something.
Open source is about developers scratching their itch. When somebody
really *wants* to use Giac and Sage, so much that they are willing
to do the work right to make the two work together and maintain it,
then it will hopefully happen. Before then it should not. I don't want
some half-assed interface in Sage from somebody who doesn't care deeply
about *both* giac and sage.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
