4 ms·

https://noyaml.com https://noyaml.com

systemvoltage 5y ago
How about no emojis? Am I the only one who finds these abominations annoying in code/docs? Slack chat? Fine. npm logs with emojis? No thanks.
- duxup 5y ago
  More emojis! (Ok not really)
- eyelidlessness 5y ago
  You’re welcome to that opinion but you’re just going to age restrict yourself and have artificially limited impact informing others ¯\_(ツ)_/¯
  - eyelidlessness 5y ago
    Okay, since this felt like common knowledge and apparently is also an unpopular opinion: emojis can and often do improve accessibility of documentation. Like any other symbolic reference in text, their use can be defined in a key and they can be used to concisely document a support matrix, or signal complexity levels of deeper links, or… even just thematically identify content in a friendly and inviting way.
    - yjftsjthsd-h 5y ago
      Do they? Even if you use them perfectly consistently, people need to know what they mean. For some really common ones that might be fine (green check mark on CI probably means the build ran successfully), but the moment anyone gets confused or doesn't recognize a symbol I feel like accessibility drops off a cliff.
      - consp 5y ago
        Considering in some cultures the meaning of red and green are somewhat reversed from westeren I would not be so sure about that. I remember being in the traffic management center in Tokyo for an arranged visit and thought the entire city had come to a halt but red was high throughput not stoppage.
  - chakkepolja 5y ago
    I am a generation Z zoomer and people using emoji in code / docs scream immaturity to me.
    - FroshKiller 5y ago
      I frequently place emoji in code files and database scripts to ensure other people aren't using the wrong encoding in their editors when working on our projects.
Dylan16807 5y ago
So there are six criticisms actually in this file, by my count. Of those, "NO" is fixed, 0 causing octal is fixed, to me that SQL syntax doesn't look any worse than the low bar set by normal SQL, and the CI providers using different schemas doesn't really have anything to do with YAML. So that leaves two complaints. I'm not immediately offended by the clock thing, like I am by NO and octal, but I don't really have the right experience to say how bad it is. And I was going to say it's bad that nesting escaped string is hard, and it's a shame when languages don't have better quoting mechanisms... then I remembered that YAML has block quotes with no need to escape inside, so that example is just wrong. And they even link later to the stackoverflow post talking about YAML block quotes. There are problems with YAML but these examples are not good ones. ((By the way, I've seen that "There are 63 different ways to write multi-line strings in YAML" link before but only took the time to fully understand it just now, and that's a gross exaggeration that makes me question the author more than it reinforces their point. There's a reason the original link says -5- -6- NINE (or 63*, depending on how you count). Block quotes have 1 or 2 characters to say what to do with newlines, then might have a digit to indicate indentation. That's "60" of the "63". I suppose if it allowed multi-digit numbers there it would be "billions" of ways to write multi-line strings in YAML? That number isn't a real criticism.))
- Dylan16807 5y ago
  I have now learned that YAML 1.2 removed the sexagesimal parsing. So scratch that one too.

How about no emojis? Am I the only one who finds these abominations annoying in code/docs? Slack chat? Fine. npm logs with emojis? No thanks.

duxup 5y ago
More emojis! (Ok not really)
eyelidlessness 5y ago
You’re welcome to that opinion but you’re just going to age restrict yourself and have artificially limited impact informing others ¯\_(ツ)_/¯
- eyelidlessness 5y ago
  Okay, since this felt like common knowledge and apparently is also an unpopular opinion: emojis can and often do improve accessibility of documentation. Like any other symbolic reference in text, their use can be defined in a key and they can be used to concisely document a support matrix, or signal complexity levels of deeper links, or… even just thematically identify content in a friendly and inviting way.
  - yjftsjthsd-h 5y ago
    Do they? Even if you use them perfectly consistently, people need to know what they mean. For some really common ones that might be fine (green check mark on CI probably means the build ran successfully), but the moment anyone gets confused or doesn't recognize a symbol I feel like accessibility drops off a cliff.
    - consp 5y ago
      Considering in some cultures the meaning of red and green are somewhat reversed from westeren I would not be so sure about that. I remember being in the traffic management center in Tokyo for an arranged visit and thought the entire city had come to a halt but red was high throughput not stoppage.
- chakkepolja 5y ago
  I am a generation Z zoomer and people using emoji in code / docs scream immaturity to me.
  - FroshKiller 5y ago
    I frequently place emoji in code files and database scripts to ensure other people aren't using the wrong encoding in their editors when working on our projects.

Dylan16807 5y ago

So there are six criticisms actually in this file, by my count. Of those, "NO" is fixed, 0 causing octal is fixed, to me that SQL syntax doesn't look any worse than the low bar set by normal SQL, and the CI providers using different schemas doesn't really have anything to do with YAML. So that leaves two complaints. I'm not immediately offended by the clock thing, like I am by NO and octal, but I don't really have the right experience to say how bad it is. And I was going to say it's bad that nesting escaped string is hard, and it's a shame when languages don't have better quoting mechanisms... then I remembered that YAML has block quotes with no need to escape inside, so that example is just wrong. And they even link later to the stackoverflow post talking about YAML block quotes. There are problems with YAML but these examples are not good ones. ((By the way, I've seen that "There are 63 different ways to write multi-line strings in YAML" link before but only took the time to fully understand it just now, and that's a gross exaggeration that makes me question the author more than it reinforces their point. There's a reason the original link says -5- -6- NINE (or 63*, depending on how you count). Block quotes have 1 or 2 characters to say what to do with newlines, then might have a digit to indicate indentation. That's "60" of the "63". I suppose if it allowed multi-digit numbers there it would be "billions" of ways to write multi-line strings in YAML? That number isn't a real criticism.))

Dylan16807 5y ago
I have now learned that YAML 1.2 removed the sexagesimal parsing. So scratch that one too.