Rosetta Code talk:Policy

idiomatic?

First off. Thanks, that is a great idea for a page!

"Solutions to tasks should be idiomatic. That is, they should represent how the user community of that programming language would wish to see the task be solved by a new, low-experience, or experienced-in-another-language programmer. "

I don't agree about making the solutions be geared at low experienced or experienced in another language programmers. Idiomatic as in "Peculiar to or characteristic of a given language" says it all. It's how the experienced and involved programmer from the languages community would agree the solution should be phrased. There may be several styles of doing something in a language and that might allow several stylistic variants, but I would wish to see how something should be solved in, say, Prolog, rather than trying to make Prolog look like C. I would want to see examples that make use of a languages extensive standard library, rather than just rewrite something, (if the task allows of course - you need to follow the task as much as possible). --Paddy3118 (talk) 21:06, 12 May 2013 (UTC)

I also don't agree about gearing solutions to (at) low-experienced programmers   (let alone, new programmers -- to me, that means novice).   I didn't think that Rosetta Code is a   See Spot Run   type of chrestomathy.   When programming in REXX (and possibly, most languages as well), that language lends itself to many "styles" of programming.   As one gets more experienced, styles change and get more sophisticated. -- Gerard Schildberger (talk) 22:55, 12 May 2013 (UTC)

Can I join in?

I hope you don't mind me adding to the page. My stuff too is preliminary and subject to edits/deletions/controversy/... :-)
--Paddy3118 (talk) 21:42, 12 May 2013 (UTC)