On Jun 4, 9:39 am, Timothy Clemans <timothy.clem...@gmail.com> wrote: > On Fri, Jun 4, 2010 at 9:28 AM, rjf <fate...@gmail.com> wrote: > > > On Jun 4, 9:07 am, Timothy Clemans <timothy.clem...@gmail.com> wrote: > >> "It seems to me that Sage is hard to use, hard to change, apparently > >> even hard to install." > > >> Since when is writing Python code hard? > > > Um, you seem to think that Sage is written in Python, and that writing > > Python code is easy. > > The Sage library is Python and Cython code.
I am sure the suppliers of all that (non-python) software that Sage calls are very flattered by your assumption that their code never needs to be fixed. > > > 1. Look at the "picture" of Sage in that paper and notice that the > > automobile is plastered with > > logos of software (open source software). How much of it is written > > in Python? C? C++? Lisp? > > Perl? Makefile-language? Assembler? etc. > > Someone writing code using the Sage library is either going to write > Python or Cython scripts. Really? Someone finding a bug in (say) Fricas would fix it by writing Python? Not Aldor or Lisp? > > > > > 2. When you say that writing Python code is easy, what are you > > comparing it to? > > Lets see PHP was a royal pain. I was able to do "interesting" stuff in > Python very quickly whereas when I tried PHP out for a few weeks > recently I couldn't wrap my head around arrays. Ah, so you are saying Python is better than PHP. But you have no familiarity with any other languages (generously calling PHP a language...)? I believe that Python, as a language, is OK. But your example, which involves running "make" and waiting a while, is hardly illustrating an "easy" programming setup. -- 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
