[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why reference SRFI's at all



So...

I was asked to post this comment here after it came up on the Ikarus users list.  

I am not a common contributor to the SRFI process, I am just some guy who uses Scheme, loves scheme and tries to encourage others to use it too.  That may seem like an irrelevant point, but I think it's essentail to understand the context of what I'm about to say.

Scheme is a powerful, elegant language.   However, I sometimes think that people go out of there way to make it hard for people to learn.

I have one simple question.   If you step back from this process, and you think about someone coming to scheme for the first time, what value is there in naming a library after the order that someone thought of the idea?   Please take the following in the good humour it is intended - I don't want to start a flame war, just make a point.

Imagine for a second I create a new language, the awesome, all powerful Perlpy Scruby, in this language I choose to name the libraries after the combination of the process used to reach the design decision and the order in which the particular design decision was made.   Therefore, in my Perlpy Scruby code you might see the following at a top of a file:

<import  <gjti <47 64 12>>>

OK, as you are all newcomers to my fictional language, I hope you're all perfectly comfortable and understand exactly what I just did.  If you don't you'll be reassured to know that there is a site, somewhere ont he internet that you can trawl through to find out what those things all mean.

I am all for standardised naming, in fact in a world with so many Scheme implementations I think it's essential, but why do we have name things after the beurocracy involved in standarising them?  It only makes sense to the people involved in this kind of discussion, not to the end users of the language.

--
Geoff Teale
<tealeg@xxxxxxxxxxxxxx>