R6RS ratification guesstimate results

I have gone through the R6RS electorate and tried to guess each elector's vote based on their statement of interest. It's been a fun exercise. Most of the statements give clear hints (such as sentences like "R6RS will" + positive action, or Felix's all-caps screaming battle cry). Other statements offer partial clues (such as insisting on minimalism, or deploring the lack of a standard library). Yet others are completely opaque (some of them reading like CVs packed with the author's numerous accomplishments), in which case I ignored them.

OK, the results: R6RS will probably pass with a 70% approval rate.

I'd be interested in seeing any other predictions, especially if anybody has closely followed the r6rs-discuss list and has some time to burn. The official results are still more than a month off.

As most of you know, I strongly oppose R6RS. I will limit myself to asking those electors who complained about Scheme's lack of structs and hash tables to go read the SRFI list and pay attention to SRFI-9 and SRFI-69. If your Scheme does not support one of the widespread SRFIs, you should ask your friendly implementor to reconsider. Also, the fact that R6RS brings some good things does not mean we need to compromise on the bad things; it's always possible to restart the standardization effort and pick the gems out of the brown stuff.

Tags: 

Comments

Having a language defined in operational semantics is very important.
Maybe I'm clueless, but my guess is that this will open the door to lisp reading lisp at an unprecedented level.
Code-walkers ahoy.
And then you can begin to have system-level software that process system-level software *as defined formally by a standard*.
Common Lisp, for instance, has not achieved this.

I suspect you may be reading more into the statements than is there. Given that many were written before the official release of R6RS, "R6RS will [insert benefit here]" appears to be a statement of "I expect R6RS to provide [insert benefit]", and if the proposal doesn't end up providing those benefits or impose other excessive penalties, then people may defeat it. I haven't decided yet.

As someone with a rather opaque submission, I do hope you're wrong. I think many were opaque simply as a matter of politeness. Not for a second have I considered voting "yes".

Well, I wonder whether you thought pro or cons of my submitted short text (pun somewhat intended), but there is the expressed opinion of a hundedth people, and the choice that will be made by hopefully many more users. I know schemers who didn't apply for some reason or another.

However, I somewhat regret that leanrning Scheme implies learning one implementation. I'd rather see in Scheme maybe more "useful" requirements, such as network (tcp/ip at least), a good time measure. How many potential users did we let go because they initially chose a Scheme implementation that didn't suit their expectations ? How many of them fled thinking "Scheme stinks ! It ain't even possible to read and write a socket !" (not even considering bidirectional ports).

Should R6RS be accepted by most of the voters, let's then hope the rest of the community won't stick to R[45]RS, or [insert your favourite Scheme implementation that rules the others, no matter what].

P!

I am just an onlooker at the moment but if you only get a 70% approval for a language change; I would reconsider the idea. I have read a few dissenting answers to the draft and if I were to vote (not that I could) I would vote a resounding no.

Well, voting is now closed and we shall know how it went in a matter of two weeks or so... I also voted against ratification.

Chris and John, that's somewhat encouraging...

Adrien (Pierard ?), I thought your statement was slightly "pro". BTW, I agree that things like TCP, binary I/O etc need to be standardized, but I believe the correct process is via SRFIs. That's how we got hash tables, byte vectors, a thread API and countless other goodies that can be widely used across implementations. Very few things need to be solved at the language level (like cleaning up the mess that ensued when R5RS unwisely removed define-macro).