Rosetta Code:Village Pump/Task titles: Difference between revisions

(→‎Proposal: my comments)
Line 36:
:: I disagree. On the principle of not omitting articles, "Insert element" ought to be "Insert an element". But "Define element" can't be "Define an element", of course; it would have to be "Define the element type", and by that point I think we're better off with just plain old "Element definition". —[[User:Underscore|Underscore]] ([[User talk:Underscore|Talk]]) 15:29, 1 February 2010 (UTC)
::Personally, I think the doubly-linked list tasks should simply be merged into a single task. (Same for the singly linked list tasks.) --[[User:IanOsgood|IanOsgood]] 17:27, 1 February 2010 (UTC)
::: Agreed; there's no sense in having them split up like this when they're so dependent upon one another. —[[User:Underscore|Underscore]] ([[User talk:Underscore|Talk]]) 22:55, 1 February 2010 (UTC)
 
: That list is a little hard to read. It'd help if we somehow highlighted where changes are proposed at all, and further differentiated between minor changes (e.g., case, addition/subtraction of small words like “a”) and more major ones (e.g., “Basic Animation” to “Animation”, which might cause issues later). We can expedite the minor changes easily enough, but the major ones require consideration of what we actually want to achieve. –[[User:Dkf|Donal Fellows]] 15:51, 1 February 2010 (UTC)
Line 58 ⟶ 59:
:*Keep "User output/*" (since we use "Goodbye world" anyway)
:--[[User:IanOsgood|IanOsgood]] 17:27, 1 February 2010 (UTC)
::* Me neither. Suggestions, anyone?
::* I don't think so, if we're going to distinguish list operations from loops. I think this is the "Map" task you want; should we just name it that?
::* I understand your thinking, but let me make clear that my intention in using titles with slashes is ''not'' to duplicate the function of ordinary MediaWiki categories. That would be pointless. The idea is rather to note tasks that are interdependent or that have largely parallel goals. "Bitwise operators" demonstrates AND, OR, etc., not addition etc., so it doesn't belong in "Arithmetic/*".
::* Yeah, "Sorting algorithms/*" is probably an improvement. Changed.
::* See my comments about "Bitwise operations".
::* Again, good idea, but I don't know what to use instead.
::* Agreed; changed. (The articles which belong to [[:Category:Raster graphics operations]] but which I didn't put in "Bitmap/*" are those which don't depend on [[Basic bitmap storage]].)
::* Okay, but which process? "Fork the current process"?
::* "Machine address" makes me think the task has to do with finding the address of a machine.
::* Man, I just don't know. I'm not sure how much we should insist that tasks with names like "map", "filter", and "reduce" use actual list operators instead of loops.
::* But [[Null]] isn't about literal undefined values, it's about checking to see if a variable is defined. Hence my choice.
::* What other task does it duplicate?
::* Some of the examples are complete proofs which the software in question verifies. This is distinct from automated theorem proving, in which the software writes the proof itself.
::* But an example doesn't have to interpret. It could also compile. The objective of each of these tasks is just to execute some code; how an example does it is up to the implementer.
::* Agreed; changed.
::* The task's scope is somewhat greater than that. Maybe "Literals/Boolean" should be a redirect?
::* I think a newbie is much more likely to gather what the purpose of the task is if it's called "Hello world". "User output" is misleading because we generally use the word "user" to mean somebody who runs a program, not writes it. The use of "goodbye" instead of "hello" is almost meaningless. Probably we should change the task to use "hello"; Rosetta Code has gotten a lot more serious since the days it was named Goodbye World.
::—[[User:Underscore|Underscore]] ([[User talk:Underscore|Talk]]) 22:55, 1 February 2010 (UTC)
 
===Exception?===
Line 64 ⟶ 83:
At one time, it was noted in the blog that we had no tasks beginning with the letters K and Y. I remember it was close to Xmas too, and created the [[Yuletide Holiday]] task to fill a need where the name was important. Could I most humbly ask that the name be changed to just have a lower-case H becoming: ''Yuletide holiday''? (The same applies to [[Knapsack Problem]], but you already seem to be set to change it to ''Knapsack problem'' with a lower-case p). Thanks --[[User:Paddy3118|Paddy3118]] 07:05, 1 February 2010 (UTC)
: But you also made [[Y combinator]], which I intend to leave alone. That ought to cover it, right? :) At any rate, don't forget that "Yuletide holiday" will hang around as a redirect until someone deletes it, and while I have the power to do that, I have no plans to. —[[User:Underscore|Underscore]] ([[User talk:Underscore|Talk]]) 15:29, 1 February 2010 (UTC)
 
===If you disagree…===
My real goal, at least for the moment, is just to impose some conventions on Rosetta's titles as a whole, not to worry about individual titles. So if you disagree with some of my (necessarily) arbitrary selections and find my justification for them unconvincing, you can change [[Rosetta Code:Village Pump/Task titles/List|the list]] yourself. When I run UnderBot, I'll use whatever's there. —[[User:Underscore|Underscore]] ([[User talk:Underscore|Talk]]) 22:55, 1 February 2010 (UTC)
845

edits