4 ms·

I want to snidely remark in an HN thread that if you make a thing that generates visual output, you should show some examples of that output.

xiconfjs 4y ago
owner replied with "Ask GitHub to support insertion of SVG into their Markdown". Perhaps "screenshots" of the output in jpg or png are fine, too.
- deleted 4y ago
  [deleted]
- boesboes 4y ago
  You can just use svg files in github markdown afaik
ainar-g 4y ago
I've tried it with the logo diagram: .-------------------------. | | | .---.-. .-----. .-----. | | | .-. | +--> | | <--| | | | '-' | | <--| +--> | | | '---'-' '-----' '-----' | | ascii 2 svg | | | '-------------------------' A screenshot of the resulting SVG in the GNOME Image Viewer: https://imgur.com/I6NySZp https://imgur.com/I6NySZp.
sokoloff 4y ago
That might be 2% snide, but it’s 98% practical advice.
mcphage 4y ago
That's not even snide, that's just... basics. Otherwise why waste peoples' attention?
- wtetzner 4y ago
  What an odd perspective. Someone built a tool they thought was useful, and released it under the MIT license in case other people might benefit from it, but not putting a screenshot in the README is wasting people's attention?
  - mcphage 4y ago
    Yeah. "Hey, come look at this thing! It's really great, and makes pretty pictures, but you'll have to trust me on that. Sure, it's worth your time to figure out the issues; my lack of attention to the readme definitely hasn't extended to making this work on machines other than mine, honest."
    - wtetzner 4y ago
      I think you might be reading into it too much. Unless the README really is saying you should use it, as opposed to just describing what it is.
      - mcphage 4y ago
        The readme is there to tell people what the project is about, why they should use it, and the basics of doing so—yes, absolutely. How are you going to get anybody to use your project or contribute to it if you can’t (or don’t) even make it clear why they should care?

xiconfjs 4y ago

owner replied with "Ask GitHub to support insertion of SVG into their Markdown". Perhaps "screenshots" of the output in jpg or png are fine, too.

deleted 4y ago
[deleted]
boesboes 4y ago
You can just use svg files in github markdown afaik

ainar-g 4y ago

I've tried it with the logo diagram: .-------------------------. | | | .---.-. .-----. .-----. | | | .-. | +--> | | <--| | | | '-' | | <--| +--> | | | '---'-' '-----' '-----' | | ascii 2 svg | | | '-------------------------' A screenshot of the resulting SVG in the GNOME Image Viewer: https://imgur.com/I6NySZp https://imgur.com/I6NySZp.

sokoloff 4y ago

That might be 2% snide, but it’s 98% practical advice.

mcphage 4y ago

That's not even snide, that's just... basics. Otherwise why waste peoples' attention?

wtetzner 4y ago
What an odd perspective. Someone built a tool they thought was useful, and released it under the MIT license in case other people might benefit from it, but not putting a screenshot in the README is wasting people's attention?
- mcphage 4y ago
  Yeah. "Hey, come look at this thing! It's really great, and makes pretty pictures, but you'll have to trust me on that. Sure, it's worth your time to figure out the issues; my lack of attention to the readme definitely hasn't extended to making this work on machines other than mine, honest."
  - wtetzner 4y ago
    I think you might be reading into it too much. Unless the README really is saying you should use it, as opposed to just describing what it is.
    - mcphage 4y ago
      The readme is there to tell people what the project is about, why they should use it, and the basics of doing so—yes, absolutely. How are you going to get anybody to use your project or contribute to it if you can’t (or don’t) even make it clear why they should care?