Template talk:Eff note

I don't like the premise of this template. It seems to me that there are various reasons besides "efficiency" (e.g. readability, idiom, extensibility, ...) that one might have a "but you should do it this way instead" note. I also think that "pretentious-sounding" is the example author's problem. I am concerned that trying to fit things into this bin (or not) will create visual noise (from the messagebox look; this is not a "needs fixing" kind of thing like the other messageboxes) and semantic noise (in that it's a strong formalized statement when a simple short sentence or even clause would do better). --Kevin Reid 21:20, 31 August 2009 (UTC)

Agreed. —Donal Fellows 12:32, 1 September 2009 (UTC)

Also don't care for the template. An example need not be efficient to be illustrative (If that were the case, the basic bitmap storage task would be unforgivable...). If efficiency is desired, but not mandated by the task description, it should be considered whether it be provided as an additional solution for side-by-side comparison. If the task description is written in a way that denies efficiency (as the basic bitmap storage task is), and an efficient approach is desired, I don't see a problem with creating a task for the purpose. --Short Circuit 14:41, 1 September 2009 (UTC)

I made this template because I saw little notes on examples that seemed to say "my language is so awesome that I consider this task 'stupid to do' in it" or at least "I don't even know why you're thinking about doing this in my language, but here's how in case someone is holding a gun to your head." I know they didn't say that directly (and maybe the authors didn't even think that when they wrote the notes), but I wanted to avoid any accidental "reading between the lines" that happened when I saw the comments. If no one wants this, they can undo the four or five edits that put them in and get rid of it. I can just keep grumbling to myself. --Mwn3d 14:57, 1 September 2009 (UTC)