Talk:Easter egg

"Task" removed

I have removed the {{draft task}} tag.
I have no problem with this being a "novelty find" somewhere on rosetta code, but it has no value in comparing languages and therefore should not be in "the task list".
Of course, there is something amusingly appropriate about it being a bit of an easter egg in itself. --Pete Lomax (talk) 12:32, 8 January 2021 (UTC)

Hmm, it still shows up, should eg {{header|Phix}} be frowned upon/banned on such a page? --12:50, 8 January 2021 (UTC)

If you remove the language headers, then it will effectively orphan the page.

If you don't think it should be a task (can't say I'm bothered either way), then it needs to be deleted altogether. Suggest we leave it to Thundergnat to decide as it will probably mess up the figures for his weekly summaries if it's left as it is. --PureFox (talk) 13:21, 8 January 2021 (UTC)

Sure, slight preference for "orphaned page" over "deleted" for me, tg. --Pete Lomax (talk) 13:45, 8 January 2021 (UTC)

I'm pretty much ambivalent about it. It probably shouldn't be a Task; like Petelomax++ says, it (almost by definition) isn't really useful information. Besides, the definition of what counts as an "Easter egg" is pretty vague. For instance: a lot of what the Python entry counts as "Easter eggs" don't seem to be part of the core functionality; nearly all require importing some module, and an awful lot of it comes across as religious dogma rather than "a nominally amusing undocumented function/feature" (to me at least). And Raku violates most of them either incidentally or as a core principal. ¯\_(ツ)_/¯

I am mildly against leaving it as a stand alone page, especially if it uses the task header markup on it. Anything that uses the =={{header|whatever}}== template gets counted as a task entry no matter if it is on a "Task" page or not. Not just by my summarizing scripts, but by the Rosettacode parsing logic, so they show up in the individual language category page as "completed tasks". I suppose I could add logic to my scripts to filter them out again but it will turn a script doing a single database request into one doing a database request and then another 812 requests for each language to get accurate filtering. Really, IMO, if someone feels strongly it should be available, they should put it on the individual language Category page. If we DO elect to keep it, I may want to look into generating a custom template for non tasks. --Thundergnat (talk) 21:37, 8 January 2021 (UTC)

Ok, I went and dug through the defined templates and found a useful one: Template:Example. =={{example|task=(Task name)|language=(Language name)}}== I think it was originally intended for sub pages where the actual implementation of a task is on its own language specific sub page, but it works fine for this too, so my reservations against leaving it as a separate page are removed. All existing entries updated. --Thundergnat (talk) 22:04, 8 January 2021 (UTC)