My favorite RCRs...

[Hal Fulton]

This is just to stir things up a little. Go to rcrchive.net and vote
for/against the RCRs there.

Hey, it beats reading another thread about P*thon or d*tabases.

My personal favorites (and yeah, one of them is mine):


#244: Limit recursion depth of Array#flatten (submitted by
matthias_georgi)

#241: in operator (submitted by hal9000)

#237: named capture with assignment in regexp (submitted by akr)

#231: Kernel#singleton_class (submitted by dblack)

#223: require a directory (submitted by mgarriss)

#213: Extended Access to the DATA Pseudo-File (submitted by austin)

#180: Warning framework (submitted by Paul Brannan)


There are also some others I voted for... not to mention some I voted
against and some I didn't understand.



Cheers,
Hal

 

[James Britt]

This is just to stir things up a little. Go to rcrchive.net and vote
for/against the RCRs there.

I just took a look (well, actually, I stopped by www.rcarchive.com
first; quite entertaining), and ran into an interesting usability issue.

The RCR pages invite you to comment on the requests; it's a wiki, after
all, but it isn't until after one has loaded the edit page, entered
well-considered (and carefully spell-checked) comments, and hit the Save
button, that one discovers that a user name and password will be required.

Maybe, where is says "Comment on this RCR (edit wiki page)", there
should be something about this?

(Do I have to submit an RCRCR for this? Will I need a user name and
password?)


James

 

[Simon Strandgaard]

I just took a look (well, actually, I stopped by www.rcarchive.com
first; quite entertaining), and ran into an interesting usability issue.

The RCR pages invite you to comment on the requests; it's a wiki, after
all, but it isn't until after one has loaded the edit page, entered
well-considered (and carefully spell-checked) comments, and hit the Save
button, that one discovers that a user name and password will be required.

Maybe, where is says "Comment on this RCR (edit wiki page)", there
should be something about this?

I did the exact same first time I used rcrchive.

(Do I have to submit an RCRCR for this? Will I need a user name and
password?)

I think David Black is maintaining rcrchive..


BTW: What happened to the happy/bad faces that were in the past on rubygarden ?
These gave a good overview of the rcr status.

 

[Jean-Hugues ROBERT]

I just took a look (well, actually, I stopped by www.rcarchive.com first;
quite entertaining), and ran into an interesting usability issue.

The RCR pages invite you to comment on the requests; it's a wiki, after
all, but it isn't until after one has loaded the edit page, entered
well-considered (and carefully spell-checked) comments, and hit the Save
button, that one discovers that a user name and password will be required.

Maybe, where is says "Comment on this RCR (edit wiki page)", there should
be something about this?

(Do I have to submit an RCRCR for this? Will I need a user name and
password?)


James

Hi,

That must have been a not so nice experience.

Is there any reason why a user/password is required? A lot of
Wikis don't need any and they work well I think.

Yours,

Jean-Hugues

 

[David Alan Black]

Hi --

Answering both James and Jean-Hugues:


Unless you read the instructions The welcome page of RCRchive says
"If you want to add comments to them [RCRs], you must subscribe to
RCRchive", with a link to the sign-up page. I guess I could add
something later in the process too.

That must have been a not so nice experience.

Is there any reason why a user/password is required? A lot of
Wikis don't need any and they work well I think.

RCRchive is really only a Wiki by virtue of piggy-backing on (a hacked
version of) RuWiki. It's not really conceived of as typically
Wiki-esque. As for usernames: I really disliked all the anonymous
posts on Ruby Garden. It was very hard to follow a discussion, and I
didn't see any reason to duplicate that experience on RCRchive. I
also like the idea of erecting at least a small barrier to entry, to
discourage the ultra-casual level of participation (particularly as
regards submitting RCRs, but also discussion).


David

 

[Jean-Hugues ROBERT]

About the need to register before posts at www.rcarchive.com

RCRchive is really only a Wiki by virtue of piggy-backing on (a hacked
version of) RuWiki. It's not really conceived of as typically
Wiki-esque. As for usernames: I really disliked all the anonymous
posts on Ruby Garden. It was very hard to follow a discussion, and I
didn't see any reason to duplicate that experience on RCRchive. I
also like the idea of erecting at least a small barrier to entry, to
discourage the ultra-casual level of participation (particularly as
regards submitting RCRs, but also discussion).

David

Anonymous posts is bad etiquette, I agree.
I tend to use -- + the CamelCase for my name to sign. I then can provide
more info about me in the referenced page, if I want. Kind of a
"Wikiish registration".

Regarding the small barrier of entry, I believe an OCR barrier would be
big enough and could block bots too. But that's your place ;-)

Yours,

-- JeanHuguesRobert