-Original Message-
From: Alexander Johannesen alexander.johanne...@gmail.com
Sent: Nov 1, 2010 9:33 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Let's go somewhere [was PHP vs. Python...]
...
So this is not a *dumb* idea, nor is it one of simply saying it's the
API, stupid
Some of us have been doing a good job introducing new concepts and processes
by writing to, or discussing with, fellow librarians.
Many of us have been in the situation where a librarian who doesn't want a
change (i.e. add homework and work for her/his load) would hide that by
saying 'I don't
Peter -
I was bewildered at the notion of needing yet another scripting
language, let alone one as library domain-specific (that wording
alone throws up red flags everywhere), but I'm not here to bash ideas.
Instead I looked up your site and read the small blurb about Nova.
It seems that the main
I would be very unlikely to use someone's homegrown library specific
scripting language.
However, if you want to make a library for an existing popular scripting
language that handles your specific domain well, I'd be quite likely to
use that if I had a problem with your domain and I was
@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Let's go somewhere [was PHP vs. Python...]
Reply-To: Code for Libraries CODE4LIB@LISTSERV.ND.EDUmailto:
CODE4LIB@LISTSERV.ND.EDU
I would be very unlikely to use someone's homegrown library specific
scripting language.
However, if you want to make a library
On Tue, Nov 2, 2010 at 5:03 AM, Jonathan Rochkind rochk...@jhu.edu wrote:
I would be very unlikely to use someone's homegrown library specific
scripting language. However, if you want to make a library for an existing
popular scripting
language that handles your specific domain well, I'd be
On Oct 30, 2010, at 10:50 AM, Peter Schlumpf wrote:
And you are correct in pointing out that the natural response of librarians
to a problem is to seek consensus in a self-absorbed way. Form committees
and all that nonsense which never goes anywhere. They are happy enough going
around in
Bill, you hit a nail pretty squarely on the head. I believe this decades long
fetish with MARC has to go. It was designed to efficiently store data on
magtapes and doesn't make any sense in today's world. It's a huge millstone
around the neck of Libraryland and it keeps them stuck in that
What's wrong with the library world developing its own domain language?
EVERYTHING!!!
We're already in a world of pain because we have our own data formats and
ways of dealing with them, all of which have basically stood idle while 30
years of advances computer science and information
