Library community programming is heavy on the string processing, right?
So, just use a language that's good for that.
Anyway, once you learn one, it's faster to learn another.
On Mon, Jul 29, 2013 at 11:57 AM, Peter Schlumpf <[log in to unmask]>wrote:
> Python and Ruby (and any other programming languages) are just tools.
> Some do some things better than others.
> Imagine if the library community had its own programming/scripting
> language, at least one that is domain relevant. What would it look like?
> Peter Schlumpf
> -----Original Message-----
> >From: Joshua Welker <[log in to unmask]>
> >Sent: Jul 29, 2013 10:43 AM
> >To: [log in to unmask]
> >Subject: [CODE4LIB] Python and Ruby
> >Not intending to start a language flame war/holy war here, but in the
> >library coding community, is there a particular reason to use Ruby over
> >Python or vice-versa? I am personally comfortable with Python, but I have
> >noticed that there is a big Ruby following in Code4Lib and similar
> >communities. Am I going to be able to contribute and work better with the
> >community if I use Ruby rather than Python?
> >I am 100% aware that there is no objective way to answer which of the two
> >languages is the best. I am interested in the much more narrow question of
> >which will work better for library-related scripting projects in terms of
> >the following factors:
> >-existing modules that I can re-use that are related to libraries (MARC
> >tools, XML/RDF tools, modules released by major vendors, etc)
> >-availability of help from others in the community
> >-interest/ability of others to re-use my code
> >Josh Welker
> >Information Technology Librarian
> >James C. Kirkpatrick Library
> >University of Central Missouri
> >Warrensburg, MO 64093
> >JCKL 2260