Xenharmonic Wiki talk:Conventions: Difference between revisions
m →Informal poll: updated voter totals |
|||
| Line 19: | Line 19: | ||
:: No, we should not imitate "FREEZE artefacts." FREEZE artefacts are just things that I screwed up. We should make it right. [[User:Mike Battaglia|Mike Battaglia]] ([[User talk:Mike Battaglia|talk]]) 20:20, 30 September 2018 (UTC) | :: No, we should not imitate "FREEZE artefacts." FREEZE artefacts are just things that I screwed up. We should make it right. [[User:Mike Battaglia|Mike Battaglia]] ([[User talk:Mike Battaglia|talk]]) 20:20, 30 September 2018 (UTC) | ||
::: As a wiki author (as in, I've _written_ one of these), the''point'' of wiki syntax '''at all''' is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have ''been'' added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings. Wiki list markup, which ''is'' implemented in this wiki, is there to allow you to concentrate on providing content. Insisting on working against the tool, i.e., the wiki, by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the '''''point''''' of using a wiki at all. [[FREEZE]] is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup ''cannot be done'' with wiki markup, it should not be there. [[User:Joemcmahon|Joemcmahon]] ([[User talk:Joemcmahon|talk]]) | ::: As a wiki author (as in, I've _written_ one of these), the''point'' of wiki syntax '''at all''' is to permit you to write pages quickly without having to actually write syntactically-valid HTML. If there was no utility to adding wiki markup, it wouldn't have ''been'' added at all, and we'd just be opening edit boxes to paste in HTML. Which we would all have to always get right. Which we mostly would not, and would then spend time dorking with instead of writing about tunings. Wiki list markup, which ''is'' implemented in this wiki, is there to allow you to concentrate on providing content. Insisting on working against the tool, i.e., the wiki, by forcing HTML markup is counterproductive because it doesn't need to be done, and doing it is slower to write, and harder to update. And updating is the '''''point''''' of using a wiki at all. [[FREEZE]] is not a standard. It was a programming shortcut; insisting that it's a reason to hardcode HTML smacks of "I want to do this so I'm finding a reason" not "there is no other way to do this so I've adopted this workaround". There is no need for a workaround. Use the tools. Unless the markup ''cannot be done'' with wiki markup, it should not be there. [[User:Joemcmahon|Joemcmahon]] ([[User talk:Joemcmahon|talk]]) | ||
:::As I said, I'm not using some old fashioned, rusty <code>wikispaces</code> syntax. [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 05:28, 1 October 2018 (UTC) | |||
== What is the "Xenharmonic Wiki" Namespace for? == | == What is the "Xenharmonic Wiki" Namespace for? == | ||