Wikipedia:Miscellany for deletion/Template:Qif


 * The following discussion is an archived debate of the proposed deletion of the miscellany page below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the page's talk page or in a deletion review).  No further edits should be made to this page.  

The result of the debate was Keep until testing of is completed, then Deprecate. Nacon kantari  e |t||c|m 02:36, 3 May 2006 (UTC)

Template:Qif

 * Upon completion of this MfD, and should the decision be to delete, this template should be placed in Templates for deletion/Holding cell.

First off, I need to explain why this is on MfD, not TfD. qif is not just any old template; it's one of the most commonly used templates on Wikipedia. It's effectively become a piece of Wikimarkup in itself. As such, I feel listing this on TfD would be inappropriate; qif does not fit the mold of traditional templates.

This template should now be deprecated so that we can use the syntax available in Wikimarkup. Doing so would put considerably less strain on the servers, slightly reduce exposure to vandalism (if a rogue admin decides to crash Wikipedia, he can't do it by editing a meta-template), etc. Some people appear overly attached to qif, so I feel getting a broader consensus on this would be appropriate. To me, it is obvious that we now have something better, so why not officially deprecate qif? Johnleemk | Talk 15:50, 18 April 2006 (UTC)


 * Note: For specific information about #if:, see ParserFunctions.


 * Delete. Obsolete, redundant, a total fire hazard. — Apr. 18, '06 [15:54] <[ freakofnurxture]|[ talk]>
 * Question: how is this a fire hazard once it is deprecated and orphanned? Why can't we keep it as a historical template, duly marked as deprecated and with a thick pointer to the docu of ParserFunctions? --Ligulem 20:52, 18 April 2006 (UTC)
 * Addendum: qif was the central target of WP:AUM. WP:AUM was said to not be deleted because it was once a policy, as policies do not get deleted (I was told). As WP:AUM was primarily created against qif, shouldn't qif be kept in the same way as historical as WP:AUM? --Ligulem 20:59, 18 April 2006 (UTC)
 * Pardon me for assuming bad faith, but I don't think keeping it in the template namespace would be a good idea. It wouldn't stop people from using it. I'm just barely gaining ground in the orphaning process as it is. — Apr. 19, '06 [02:31] <[ freakofnurxture]|[ talk]>
 * Factually untrue - AUM predates qif by months. Phil Sandifer 21:12, 18 April 2006 (UTC)
 * Factually equally untrue as qif is the successor of deleted template:if, which was blanked and protected by you while I was in the middle of migrating hundreds of templates to the server friendlier qif. So much per the history. --Ligulem 21:27, 18 April 2006 (UTC)
 * Another problem: We do have a set of once highly used category:Deprecated citation templates which are no longer used but in talk archives and the like. These break when qif is deleted. What should be done with them? Please note that they cannot be substed because qif cannot be substed. As a side note: a template using #if looks equally awful when substed. --Ligulem 21:07, 18 April 2006 (UTC) --Ligulem 21:52, 18 April 2006 (UTC)
 * Cosmetics are only a concern in the article namespace. Ideally, no templates should be substed into the article namespace anyway. Using parser functions we can reduce these some of these ridiculous 5+ layer deep templates to a single call, and use them, as Pathoschild puts it, practically for free. — Apr. 19, '06 [02:31] <[ freakofnurxture]|[ talk]>
 * Delete. We no longer have a use for it, and it's a massive potential problem. I'm happy to proffer the services of my bot to substitute it. James F. (talk) 15:56, 18 April 2006 (UTC)
 * No job for a fully automatic bot. Suggest using AWB instead. For example, due to a bug in ParserFunctions, I couldn't convert Template:Harvard citation from qif to #if. --Ligulem 22:46, 18 April 2006 (UTC)
 *  Delete (see below); many of the developers have expressed a significant preference for the native wikimarkup syntax over the conditional metatemplates. As I understand it, the conditional metatemplates use multiple calls to the database, which is expensive in terms of server resources. On the other hand, ParserFunctions are performed entirely by the Parser, and with cacheing they would be literally free in terms of server resources for most operations. // [ admin ] Pathoschild (talk/map) 15:57, 18 April 2006 (UTC)
 * I'm changing my vote to 'Delete when glitches with ParserFunctions are resolved'. I'm particularly referring to the   glitch in  , which prevents the conversion of certain templates. // [ admin ] Pathoschild (talk/map) 23:20, 18 April 2006 (UTC)
 * Conditional delete if #if is here to be. → A z a  Toth 15:58, 18 April 2006 (UTC)
 * Keep for now. Yes this should absolutely be deprecated... after the new '#if:' feature is no longer in a trial period. It has only been a week and ParserFunctions has had several features added, removed, or changed. The #if: function itself has been changed to work differently than it did originally. Further, the supposed 'server load' problems of qif simply aren't problems... at least according to the lead developer and the observed reality of qif now being used vastly more than it was in the past and yet causing no trouble. Wait until the new methodology is stable and then deprecate the old. --CBDunkerson 16:03, 18 April 2006 (UTC)
 * Conditional delete per AzaToth, if condition(s) not met, then Keep per CBDunkerson. —Locke Cole • t • c 16:08, 18 April 2006 (UTC)
 * Changing to Keep per ; this template is of interest historically, so I strongly urge deprecating it and, once orphaned, blanking it and leaving it protected. —Locke Cole • t • c 06:38, 19 April 2006 (UTC)
 * See also: Templates for deletion/Log/2006 April 18 —Locke Cole • t • c 16:10, 18 April 2006 (UTC)
 * Keep until all uses are replaced by, as per CBDunkerson. ericg &#9992; 16:20, 18 April 2006 (UTC)
 * Err. The point of this discussion is to decide whether we should start replacing its use, as doing so is such a major operation. James F. (talk) 16:27, 18 April 2006 (UTC)
 * Yet the discussion is under "Miscellany for deletion. ericg &#9992; 21:29, 18 April 2006 (UTC)
 * Yes. That's so that we get an actual decision made, and that people other than those who created the template (and so would prefer to keep it, probably) get to see the discussion; the VP is useless for such things, and has been for years. James F. (talk) 21:56, 19 April 2006 (UTC)
 * Ahem. For the record, the above statement and Johnleemk's, "Some people appear overly attached to " are both completely uncalled for. The creator of this template was AzaToth... who then went and put together a MediaWiki alternative very similar to what Tim eventually installed. Other leading proponents of 'qif' have been Locke Cole and myself... both of whom were also very involved in supporting the #if: replacement prior to it's installation and amongst the first to start converting templates over to it. I believe my response to the initial proposal should sufficiently establish 'support' for the idea. Contrary to various innuendos and outright insults the only person I have seen arguing against the use of #if: is Netoholic... the leading opponent of QIF. I did suggest that it would be prudent to hold off on mass conversions until the 'trial period' was over, but since some users are determined to save us from the (largely fictional) evils of 'qif' that ship has sailed and we'll just have to hope that there are no further format changes to #if: or other issues with it. So to sum up... this is not the 'great crusade against the promoters of QIF' that you paint it. The promoters of QIF were actively involved in testing and implementing #if: as a means of replacing QIF. We were the ones who lobbied for this change. Please drop the attitude. --CBDunkerson 22:38, 19 April 2006 (UTC)
 * Conditional delete provided that the devs decide to keep ParserFunctions enabled. Kirill Lok s h in 16:52, 18 April 2006 (UTC)
 * Deprecate and Keep . This is a historic template and access to it should be fully preserved. I will happily help with WP:AWB orphanning. I trust Tim not to pull the plug on #if. #if works and it's time to use it. --Ligulem 16:54, 18 April 2006 (UTC)
 * ...and blank and protect (after having seen a lot of substing of qif-using-templates). --Ligulem 19:55, 27 April 2006 (UTC)
 * Delete per Freakofnurture and JamesF. --Interiot 17:00, 18 April 2006 (UTC)
 * Delete - ditto. Someoneinmyheadbutit&#39;snotme 21:26, 18 April 2006 (UTC)
 * Delete when user:Tim Starling says that the testing period for ParserFunctions is successfully completed. As a developer myself, I worry about premature deletion of working software. Let's be guided by Tim on this one. --Uncle Ed 17:09, 18 April 2006 (UTC)
 * (*fD is showing us what a straitjacket it is again :). Here the logical thing to do is to 1) get the word from Tim that the expression syntax is stable (we don't care about implementation but syntax is important) and then 2) migrate slowly but surely across to the new syntax (using e.g. JamesF's bot) making sure everything works as expected. So that's somewhere in between keep and delete I suppose :). Pcb21 Pete 17:41, 18 April 2006 (UTC)
 * See my comment to ericg, above. James F. (talk) 21:56, 19 April 2006 (UTC)
 * Ok, my answer is "yes, I would like us to start the migration." Pcb21 Pete 22:53, 19 April 2006 (UTC)
 * Neutral I think this nomination is premature until Tim Starling has completely and fully tested m:ParserFunctions so it is 100% more stable and efficient than qif. Zzyzx11 (Talk) 18:05, 18 April 2006 (UTC)
 * Keep and relist IFF #if is made permenant. — xaosflux  Talk  18:57, 18 April 2006 (UTC)
 * Keep per xaosflux and CBDunkerson. &mdash; Saxifrage &#9998; 20:22, 18 April 2006 (UTC)
 * Delete as useless now that better options are available. --Jannex 20:29, 18 April 2006 (UTC)
 * Deprecate and Keep once the testing period for ParserFunctions is completed. —Doug Bell talk•contrib 20:46, 18 April 2006 (UTC)
 * Keep. As I understand it, the ParserFunctions are still on trial (debug?) mode, so they're not completely stable, so start slowly deprecating it while keeping the template for backup purposes. I've got no objection to deleting it once it is reasonably safe to assume that any potential bugs have been quashed. Tito xd (?!? - help us) 21:22, 18 April 2006 (UTC)
 * Repeat after me: NOONE IS SUGGESTING THAT THIS BE DELETED WITHOUT FIRST BEING MIGRATED TO PARSERFUNCTIONS AND THOROUGHLY ORPHANED. Go on, repeat it. -Splash talk 21:31, 18 April 2006 (UTC)
 * NOONE IS SUGGESTING THAT THIS BE DELETED WITHOUT FIRST BEING MIGRATED TO PARSERFUNCTIONS AND THOROUGHLY ORPHANED. Done. --Ligulem 21:36, 18 April 2006 (UTC)
 * WHO THE HELL IS NOONE AND SINCE WHEN HAS HE BEEN IN CHARGE OF WIKIPEDIA? Pcb21 Pete 21:44, 18 April 2006 (UTC)
 * Read after me: THE CABAL → A z a  Toth 21:46, 18 April 2006 (UTC)
 * Then why are we bothering with a delete discussion? Templates can be migrated without a discussion to delete qif.  There is also the historical compatibility issue, which is a further argument to migrate and deprecate, but KEEP.  So, repeat after me, IT IS PREMATURE TO DISCUSS DELETION AT THIS POINT.  Contrary to what some people seem to think, the Wikipedia servers are not going to spontaniously combust if this template isn't immediately deleted. —Doug Bell talk•contrib 23:22, 18 April 2006 (UTC)
 * Keep -- I hate to say this, since by all accounts the new syntax is what we've been demanding. But the heavy use of this tool positively asserts its importance. By all means, deprecate its use -- as publicly as possible. Every possible place where an editor might go to learn about writing templates should have clear instructions that point out the currently accepted method and the interactions with substitution. Blank {qif} once orphaned, replace it with an obvious colored banner box notice: Do Not Use. But retain the page itself; it's not as if it consumes resources that way. It's earned its quiet retirement. Orphan of course; but that is non-trivial. I suggest that the first step is to deprecate, so the problem does not grow. A trusted team should set out to migrate templates to the new syntax -- and please avoid making other "improvements" meanwhile, despite temptation. Leave a clear record. Go slow while orphaning and allow time for problems to emerge. This is not an emergency. John Reid 22:02, 18 April 2006 (UTC)
 * Deprecate. Meta-templates are bad. Kaldari 22:40, 18 April 2006 (UTC)
 * Keep, per CBDunkerson and xaosflux. RexNL 23:08, 18 April 2006 (UTC)
 * Deprecate, and hold until all uses are fully orphaned. Ral315 (talk) 23:12, 18 April 2006 (UTC)
 * Deprecate, replace all uses with the new syntax, and delete immediately after that is done. All the other bizarre programming-type meta-templates should be given the same treatment as soon as the new parser functions allow. -- The Anome 23:18, 18 April 2006 (UTC)
 * Delete/deprecate, parser functions aren't going to be removed. ed g2s &bull; talk 23:30, 18 April 2006 (UTC)
 * That might be more convincing if some of them hadn't been removed already... --CBDunkerson 01:16, 19 April 2006 (UTC)
 * Comment for the records: CBD is referring to the removal of the random function by Tim . It is pretty obvious that there is no way back for Tim to remove #if. If he would remove #if why would he have created ParserFunctions then? Also the removal of #if would be fixed within 24h by the community by restoring qif (or under what name ever). --Ligulem 07:24, 19 April 2006 (UTC)
 * Deprecate, remove only when the other template works and other uses are orphaned properly. Stifle (talk) 01:23, 19 April 2006 (UTC)
 * Comment: this template deletion discussion is currently the top item on the community portal. As such, I feel it is my duty to raise my hand and say that I have no idea what this template does. Can someone please explain it in case other clueless non-developer people are coming here? If I had just stumbled across this in some random corner of Wikipedia, I'd be inclined to just mutter "not my business" and stumble on my way - but since someone put this in such a prominent place, I think we need to explain this to the hoi polloi. Johntex\talk 02:23, 19 April 2006 (UTC)
 * It implements if-then-else programming functionality using some very black magic features of the template syntax. &mdash; Saxifrage &#9998; 06:08, 19 April 2006 (UTC)
 * does the same thing, but without black magic. Kaldari 06:27, 19 April 2006 (UTC)
 * # if is part of a mediawiki-extension (the software that runs Wikipedia) named ParserFunctions. --Ligulem 08:20, 19 April 2006 (UTC)
 * Because some people do not want to understand how qif works, doesn't mean it uses black magic. qif uses current functionality of the template system. It uses m:Help:Parameter default and template paramaters, and template inclusion. Nothing else. The correctness of qif can be mathematically proven. Simple thing for basic logic. Some people were just surprised that these basic things can be used to create qif. qif has already been there. Because it is possible to create it. And it's no virus, no hack and it does not rely on shaky features. Just for the records. Come on. Wikipedia is not a kindergarten. We also have articles about quantum physics. I'm sure nobody requests the removal of them only because they are not understood by the masses :-) --Ligulem 07:43, 19 April 2006 (UTC)
 * Pardon me. I should have said deep magic then. &mdash; Saxifrage &#9998; 21:11, 19 April 2006 (UTC)
 * Keep. If we don't have any rogue admins then there isn't a problem. Cynical 07:48, 19 April 2006 (UTC)
 * Keep per Pcb21 Pete, until http://en.wikipedia.org/w/index.php?title=Special:Whatlinkshere&target=Template%3AQif shows that all instances have been migrated to #if: format. --Uncle Ed 15:59, 19 April 2006 (UTC)
 * You already said delete (please scroll up). Does this replace or extend your previous decision? --Ligulem 16:56, 19 April 2006 (UTC)
 * Neither; I just like voting twice! ;-) --Uncle Ed 18:12, 21 April 2006 (UTC)
 * Keep the new code is not mature or well tested enough. Even then, I see little reason to actually delete it once it is not used. Kotepho 01:03, 20 April 2006 (UTC)
 * Keep - it's working as designed, and it's fully documented. Alternative solutions will find their way when they are debugged and documented. --&#160;Omniplex 01:48, 20 April 2006 (UTC)
 * Comment: It's actually still buggy and breaks a number of templates that require outputting the text conditionally to function. Until this is resolved, it can't replace . &mdash; Saxifrage &#9998; 20:45, 21 April 2006 (UTC)
 * Yes, and unlike direct ifdef-constructs (not the template) its wikitext ouput after substitution can be messy, for an example see Wikipedia talk:Template substitution. --&#160;Omniplex 23:25, 21 April 2006 (UTC)
 * Oh, don't get me wrong: I'm not arguing that qif is better. I'm only making the point that #if is not currently working as designed and so isn't yet ready to replace qif. I think ParserFunctions is a fabulous improvement and I hope that bug gets squashed soon so we can start using it without breaking templates. &mdash; Saxifrage &#9998; 23:35, 21 April 2006 (UTC)
 * Nor me. But I'm not yet sure about the parser functions, some string functions would be very nice, and that would get us near server side scripting. --&#160;Omniplex 14:27, 22 April 2006 (UTC)
 * Delete --Knucmo2 18:27, 20 April 2006 (UTC)
 * Keep This MfD is putting the cart before the horse. Testing of #if should finished first, then the template should be deprecated. --TheFarix (Talk) 22:41, 20 April 2006 (UTC)
 * Wait until the ParserFunctions are affirmed to be working fully and properly, then begin actively orphaning and list on TfD (concurrently). TimBentley (talk) 02:24, 21 April 2006 (UTC)
 * Keep until testing has finished, then deprecate  Will  ( E @ )  T  17:00, 21 April 2006 (UTC)
 * Keep as above. Too early.  -- WC  Quidditch   &#9742;   &#9998;  17:34, 21 April 2006 (UTC)
 * Delete - Conditionals are evil, because they present a barrier to template editors who don't have advanced programming knowledge. Simple is good. -- Netoholic @ 19:33, 21 April 2006 (UTC)
 * I take your point, but please look at my contribs for a whole bunch of templates which incorporate conditionals (and other calculations). I'm doing the programming, so that editors withou advanced programming knowledge don't have to. :-) --Uncle Ed 19:36, 21 April 2006 (UTC)
 * And am I not surprised? → A z a  Toth 20:48, 21 April 2006 (UTC)
 * Ignoring the fact that I support deprecating qif, conditionals actually make things less complicated, not more. The biggest reduction in complexity is that things can be done in fewer templates (since many optionals that would have formerly spawned offshoots of existing templates can now be included in the main template; see Mtnbox start, Mtnbox climb, Mtnbox topo, Mtnbox coor dms, Mtnbox finish, Mtnbox geology, Mtnbox start nopic, Mtnbox coor dm, Mtnbox volcano, Mtnbox UK, Mtnbox start norange, Mtnbox start nopic norange, Mtnbox prom as compared to the single template Infobox Mountain which handles everything those thirteen templates did). Further, the barrier of entry for new editors to learn is reduced thanks to articles like Qif conditionals (recently updated to document ). IMO if you think conditionals are too hard for new editors, you could help expand the existing documentation for   (and the other ParserFunctions) to make it simpler for them to learn. Finally, see Ed's comment above; many new editors won't touch templates because most of them cover everything they want them to do already. —Locke Cole • t • c 21:32, 21 April 2006 (UTC)
 * The MediaWiki software is a little complicated for the average user, but fortunately, most don't need to worry about it. I haven't looked at the code that supports   or , but I feel pretty comfortable using them nonetheless.  I think "keep it simple" is a very good goal.  Having conditionals that allow some fraction of the editors to create templates that simplify editing for others is not creating a barrier to editing, but rather is providing a valuable level of customization between "developer" and "editor".  Conditionals are actually helping "keep it simple" by providing a (very minimal) macro language for extending the wiki.  I think #if: is a very positive step forward in acknowledging this need and providing a better means to support it—and I hope that the ParserFunctions are extended somewhat—it's just a bit premature to discuss deleting qif until the issues with the current implementation are shaken out. —Doug Bell talk•contrib 16:29, 24 April 2006 (UTC)
 * "Machines are evil, because people who don't know how they work can't fiddle with them." Bah. John Reid 23:00, 1 May 2006 (UTC)
 * Deprecate then delete once all instances have been replaced, per above discussion – Gurch 16:06, 22 April 2006 (UTC)
 * Keep for now, but delete once most uses of {qif} have been replaced by {#if} Lankiveil 04:20, 23 April 2006 (UTC)
 * Keep the new code is not mature or well tested enough. Even then, I see little reason to actually delete it once it is not used — Preceding unsigned comment added by Megan 189 (talk • contribs) 2006-04-23 22:20:46
 * Keep until replacement is working properly. &mdash; Nightst a  llion  (?) Seen this already? 07:51, 24 April 2006 (UTC)
 * Keep for the time being. --Ter e nce Ong 14:16, 24 April 2006 (UTC)
 * Delete if the replacement is working. --Happynoodleboy 11:22, 25 April 2006 (UTC)
 * Depreciate and keep as a historical template once parser functions is fully tested. – Someguy0830 (Talk | contribs) 06:03, 26 April 2006 (UTC)
 * Delete--I tend to think that if this is deleted then we just will use #if ... I wouldn't think they'd want to mess up thousands of pages by not. Then again... it may be interesting. gren グレン 16:56, 27 April 2006 (UTC)
 * Delete. We now also have   in addition to   , to serve for another one of qif's functions. Jon Harald Søby 19:44, 27 April 2006 (UTC)
 * Comment: replaces, not . &mdash; Saxifrage &#9998; 00:27, 28 April 2006 (UTC)
 * Oh, ok. I've seen Qif being used as a switch, but I might just have a faulty memory. Jon Harald Søby 10:40, 28 April 2006 (UTC)
 * Ouch. Yes, that's entirely possible, and I imagine it was really hairy to read. :-) &mdash; Saxifrage ✎ 05:53, 1 May 2006 (UTC)
 * Defer to developer(s). An unusual vote I know, but this is something that should be their decision, since they know what they're talking about. the wub "?!"  23:20, 27 April 2006 (UTC)
 * Change to use the current syntax and keep as a mnemonic alternative to #if, possibly move to if. Parser functions are a great tool for producing automagic templates, which provide increased functionality and code readability. We should provide automagic templates for basic conditional behaviour, which should be used in settings where non-programmer editors are likely to need to read and understand the code without learning yet another syntax. The template will never be changed, so its effect on resources will be negligible. In any case, keep the history to preserve a record of a time when Wikipedia community showed its collective intelligence and resourcefulness and created a complete set of new useful behaviour out of almost nothing. Zocky | picture popups 17:49, 28 April 2006 (UTC)
 * Conditional keep. However, to discourage rogue admins, establish a rule that if anyone vandalizes the template, they will be immediately blocked for a certain amount of time. -- King of &hearts;   &diams;   &clubs;   &spades;  04:17, 1 May 2006 (UTC)
 * '''Ermm... conditionally keep, Per King Of Hearts...-- 陈 鼎  翔    贡献  Chat with Tdxiang on IRC! 04:38, 1 May 2006 (UTC)


 * The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the page's talk page or in a deletion review). No further edits should be made to this page.