| 00:16.28 | *** join/#bzflag infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 00:16.28 | *** topic/#bzflag is https://BZFlag.org || https://www.openhub.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || Current version: 2.4.18 || New shiny website! https://forums.bzflag.org/viewtopic.php?f=8&t=20201 |
| 00:16.28 | *** mode/#bzflag [+v infobot] by ChanServ |
| 00:39.51 | kierra | ~Delusional++ |
| 01:38.48 | *** join/#bzflag Sgeo__ (~Sgeo@ool-18b98455.dyn.optonline.net) |
| 02:37.52 | Flash | blast007: nothing in markdown inherently supports images, any more than HTML does. The point of markdown is to have a human-readable plain text format that can also be rendered nicer |
| 02:40.57 | blast007 | https://daringfireball.net/projects/markdown/syntax#img |
| 02:41.26 | Flash | yes, as I said, not any more than HTML does |
| 02:41.46 | blast007 | whatever. I don't understand your point. |
| 02:41.49 | Flash | to me, that would never the a primary motivation for markdown |
| 02:42.08 | blast007 | it certainly is a big use for it on Github |
| 02:42.17 | Flash | blast007: I don't think moving to markdown really adds much for our readme file |
| 02:42.18 | Flash | blast007: we're not gonna have any images, for instance |
| 02:42.24 | blast007 | have you not seen tons of repos with badges? |
| 02:42.51 | blast007 | "for instance" |
| 02:43.05 | Flash | Github is a good example of why our READMEs *should* be in markdown |
| 02:43.22 | blast007 | not really |
| 02:43.34 | Flash | we can agree to disagree then. |
| 02:43.38 | blast007 | sure |
| 02:43.39 | *** join/#bzflag Sgeo (~Sgeo@ool-18b98455.dyn.optonline.net) |
| 02:44.03 | Flash | I didn't understand your statement as you made it. Now I do. Thanks for the clarification |
| 02:45.06 | blast007 | mainly, the original PR that moved it to markdown was basically just doing it to do it |
| 02:45.25 | blast007 | it didn't really *add* anything |
| 02:45.37 | Flash | personally, I don't see any harm in adding the MD formatting to our files |
| 02:45.44 | Flash | I'm not sure why the PR was discouraged |
| 02:47.53 | blast007 | because it would affect a bunch of other systems that parse or copy the files |
| 02:48.09 | blast007 | and for what - some bold text? |
| 02:48.58 | blast007 | it looks worse when just reading the files in a text editor |
| 02:49.45 | blast007 | trying to figure out what dependencies to install on linux to build the code, and now it's wrapped in a ```sh ... ``` |
| 02:50.06 | Flash | that's bad |
| 02:50.16 | blast007 | welcome to markdown :) |
| 02:50.33 | Flash | oh, you mean the MD wrapping |
| 02:50.39 | blast007 | yeah |
| 02:50.51 | blast007 | it's a syntax for generating HTML, not really for viewing it as the markdown syntax itself |
| 02:50.55 | Flash | personal preference, I guess. That's explicit code to me |
| 02:51.22 | Flash | there's also the 4-space literal indent that is perfectly human readable |
| 02:51.29 | blast007 | just makes things less clear for people who are not aware of the markdown syntax |
| 02:52.12 | Flash | the only value in ```sh ... ``` is syntax highlighting. |
| 02:52.13 | blast007 | with markdown, we tell them to execute: `make install` |
| 02:52.21 | blast007 | but they'd have to know to not include the ` |
| 02:53.10 | Flash | on the other hand, a markdown renderer makes it perfectly clear where the verbiage and the command are |
| 02:53.13 | blast007 | so we can't use images, we can't use syntax highlighting - so what, we're left with bold text and headers? and links? |
| 02:53.31 | Flash | "we can't"? |
| 02:53.46 | blast007 | "the only value in.." makes it sound like you don't think it should be used |
| 02:54.41 | Flash | I'm saying there is an alternate syntax that is perfectly human readable. The ``` syntax adds syntax highlighting, if the renderer supports it, but less so as a human renderer |
| 02:55.31 | allejo | I'm personally for markdown. markdown has become standardized and common enough that people should know what it is. and if they don't know what it is, they read it easily on github and get benefits like syntax highlighting and linkable headings |
| 02:56.21 | Flash | I use it in all my work READMEs, and I don't even have a renderer |
| 02:56.41 | blast007 | if we did, I'd not want it to affect nearly as many files as what that PR did |
| 02:56.52 | blast007 | the readme? maybe. the rest, meh |
| 03:00.29 | Flash | ChangeLog is one I wouldn't change, but the other 16 are READMEs |
| 03:01.03 | Flash | maybe a case could be made for NEWS |
| 03:06.12 | allejo | I'd be ok with the changelog being markdown. plain text wise, it wouldn't be much difference. however on github, we'd get links to each release |
| 03:23.45 | *** join/#bzflag brad (~brad@37.187.113.104) |
| 03:23.46 | *** join/#bzflag brad (~brad@unaffiliated/brad) |
| 05:05.41 | macsforme | I think markdown makes more sense if we rewrite our README with that format in mind, and distill the information down to be more concise |
| 05:06.09 | macsforme | I wouldn't just convert what we have straight over to markdown |
| 09:01.25 | *** join/#bzflag Sgeo (~Sgeo@ool-18b98455.dyn.optonline.net) |
| 10:57.10 | blast007 | macsforme: yeah, I'd agree with that. for me, the PR didn't really do enough to justify the changeover. |
| 16:12.20 | *** join/#bzflag Sgeo_ (~Sgeo@ool-18b98455.dyn.optonline.net) |
| 21:52.37 | *** join/#bzflag spldart (~james@bzflag/contributor/spldart) |
| 21:52.38 | *** mode/#bzflag [+v spldart] by ChanServ |
| 22:33.56 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |