Rosetta Code talk:Policy: Difference between revisions

(→‎idiomatic?: Idiomatic indeed)
Line 10:
:: There's a certain level of skill that can be expected in order to tackle a particular task, I'm sure. But I'm really trying to discourage producing solutions that experts ''with that language'' can understand, as that makes it hard for anyone else to read the task solution. FWIW, I've used this site to learn a few languages, so it is ''very'' useful, and having resources aimed at people who know some languages and want to know more, that's super-valuable. Using appropriate libraries is idiomatic; I do that with Tcl solutions a lot. If a language has multiple idiomatic solutions, I see no problem in having all of them (provided they're “not too long”, which is a very fuzzy rule I know). “Idiomaticity” is the real focus, the ability to say “here, this is how the community of people who use this language think you ''should'' solve this task with this language” while also excluding performance chiseling and code golf (both of which end up producing code that's very hard to read).
:: That said, I might've not described idiomaticity correctly. That's why it's important for you guys to review and help make it say the Right Thing. –[[User:Dkf|Donal Fellows]] ([[User talk:Dkf|talk]]) 13:11, 20 May 2013 (UTC)
:: Owtz English wotz understood.--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 11:28, 21 May 2013 (UTC)
 
==Can I join in?==
2,171

edits