Comments on: Making my software open http://sarahaskew.net/2010/04/06/making-my-software-open/ sarahaskew.net Mon, 16 Jan 2012 21:47:33 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: SarahAskew » Want to build cool stuff for telescopes? http://sarahaskew.net/2010/04/06/making-my-software-open/comment-page-1/#comment-6370 SarahAskew » Want to build cool stuff for telescopes? Wed, 11 Aug 2010 11:53:30 +0000 http://sarahaskew.net/?p=2016#comment-6370 [...] Making my software open [...] [...] Making my software open [...]

]]> By: Kevin Jardine http://sarahaskew.net/2010/04/06/making-my-software-open/comment-page-1/#comment-3806 Kevin Jardine Fri, 09 Apr 2010 14:30:14 +0000 http://sarahaskew.net/?p=2016#comment-3806 I notice from your "Python sucks" tweet that you may be changing your mind about moving to Python for your next project? To a professional web developer like myself, Python seems like heaven compared to alternatives like PHP or Java (although Haskell looks pretty good as well). But I can also see that specialised languages like IDL may be easier to use (especially at first) compared to a more general purpose language like Python. I notice from your “Python sucks” tweet that you may be changing your mind about moving to Python for your next project?

To a professional web developer like myself, Python seems like heaven compared to alternatives like PHP or Java (although Haskell looks pretty good as well).

But I can also see that specialised languages like IDL may be easier to use (especially at first) compared to a more general purpose language like Python.

]]> By: Matt http://sarahaskew.net/2010/04/06/making-my-software-open/comment-page-1/#comment-3735 Matt Thu, 08 Apr 2010 00:29:22 +0000 http://sarahaskew.net/?p=2016#comment-3735 Sarah, as a quick note, Python interfaces quite nicely with both C and Fortran. Projects like f2py, fwrap, forthon, and many others all handle the Python->Fortran bridge, and we have used those in our analysis for wrapping primordial chemistry codes that are used in large scale cosmology simulations, as well as commodity algorithms like kd-Trees. Cython is amazing for wrapping C and C++ code, and things like the Boost Graph library, SWIG, SIP and others handle more advanced use cases of C and C++. Sarah, as a quick note, Python interfaces quite nicely with both C and Fortran. Projects like f2py, fwrap, forthon, and many others all handle the Python->Fortran bridge, and we have used those in our analysis for wrapping primordial chemistry codes that are used in large scale cosmology simulations, as well as commodity algorithms like kd-Trees. Cython is amazing for wrapping C and C++ code, and things like the Boost Graph library, SWIG, SIP and others handle more advanced use cases of C and C++.

]]> By: sarah http://sarahaskew.net/2010/04/06/making-my-software-open/comment-page-1/#comment-3667 sarah Tue, 06 Apr 2010 10:14:36 +0000 http://sarahaskew.net/?p=2016#comment-3667 It's my impression that the astronomy community is definitely transitioning from IDL to python, and I will certainly be making that move myself for future projects. Languages like C and Fortran will persist though, as they're much more suited to heavy numerical stuff, parallel computing etc. It’s my impression that the astronomy community is definitely transitioning from IDL to python, and I will certainly be making that move myself for future projects. Languages like C and Fortran will persist though, as they’re much more suited to heavy numerical stuff, parallel computing etc.

]]> By: Kevin Jardine http://sarahaskew.net/2010/04/06/making-my-software-open/comment-page-1/#comment-3666 Kevin Jardine Tue, 06 Apr 2010 10:05:10 +0000 http://sarahaskew.net/?p=2016#comment-3666 What do you think about the movement to shift astro software development away from proprietary systems like IDL to open source languages like Python? Eg. http://www.astropython.org/ Is this practical in the longer term, or is there just too much invested in IDL? Or is something like the GDL a better option: http://gnudatalanguage.sourceforge.net/ What do you think about the movement to shift astro software development away from proprietary systems like IDL to open source languages like Python?

Eg.
http://www.astropython.org/

Is this practical in the longer term, or is there just too much invested in IDL?

Or is something like the GDL a better option:

http://gnudatalanguage.sourceforge.net/

]]>