6 ms·

Yep, chat makes sense. Thank you for actually stating a use-case.

by uniformlyrandom 8y ago

benatkin 8y ago
Next time you see a shortened word, you can just assume it's useful. Because they are.
- uniformlyrandom 8y ago
  Not really, I have seen a lot of unneeded abbreviations. Thankfully we are (almost) out of the age of 140c messages and 40c editor lines. But more to the point, 'vulns' seems like a very unnatural abbreviation. I would go with v11n (similar to i18n).
  - warent 8y ago
    v11n meaning vulnerabilitn presumably ;)
    - NyxWulf 8y ago
      I was picturing villain with an implied evil laughter.
  - reificator 8y ago
    > But more to the point, 'vulns' seems like a very unnatural abbreviation. I would go with v11n (similar to i18n). Please no. I really don't like that convention and would rather you just type out the whole word if that's the alternative. Worse yet, for some reason you've decided to end in `n` rather than `y`. How can you dismiss the first four letters as an "unnatural" abbreviation, and then suggest inserting digits to represent the number of characters removed as an alternative? I'm not following that logic at all.
  - JeremyBanks 8y ago
    Terms like i18n and l10n are bad for a11y.
    - reificator 8y ago
      > Terms like i18n and l10n are bad for a11y. Thank you for that, I am definitely stealing that phrasing.
  - benatkin 8y ago
    Until now you apparently haven't been keeping a busy person typing in chat into account. Now you can. This use case isn't unique to the vuln/vulnerability abbreviation, but plenty of others. Including confusing ones like "i left you a vm" (virtual machine? where?).
  - deleted 8y ago
    [deleted]
  - munk-a 8y ago
    Oh please _please_ don't. i18n is a terribly obscure term with no implicit link to the actual word. This is a place where "naming things is hard" but for big concept chose short concise terminology while letting the details get lost in the verbose verbiage. Whenever I see i18n I just weep over the fact they didn't use the term "lang", internationalization is complicated and hard to shorten due to other meaningful jargon around it but there are better options than the dumpster fire which is i18n.
    - amake 8y ago
      > Whenever I see i18n I just weep over the fact they didn't use the term "lang" That's a bad idea because "lang" or "language" is already dangerously overloaded. People casually use it to mean any of (actual) language, locale (language + region (+ script, maybe)), script, or any combination of the above.
  - deleted 8y ago
    [deleted]
- warent 8y ago
  4 sr i dt ths T (for some reason I doubt that's true)
  - deoxxa 8y ago
    I read this as "for sure I do this too"
- munk-a 8y ago
  > Next time u c a shrt'd wrd u cn just ass. it's useful. B/c they r. They aren't always useful but I've rewritten your sentence in what I would consider a minimally legible format for me... but that's the problem it's for me. Don't introduce jargon in an effort to reduce comprehension time, it almost never works if you consider the time to familiarize yourself with the jargon. So when you're writing a blog post about PHP feel free to sprinkle in some comments about var vars, when you're communicating with your team use all your internal jargon... but when publishing an article for wide consumption just write everything out clearly.

Yep, chat makes sense. Thank you for actually stating a use-case.

benatkin 8y ago

Next time you see a shortened word, you can just assume it's useful. Because they are.

uniformlyrandom 8y ago
Not really, I have seen a lot of unneeded abbreviations. Thankfully we are (almost) out of the age of 140c messages and 40c editor lines. But more to the point, 'vulns' seems like a very unnatural abbreviation. I would go with v11n (similar to i18n).
- warent 8y ago
  v11n meaning vulnerabilitn presumably ;)
  - NyxWulf 8y ago
    I was picturing villain with an implied evil laughter.
- reificator 8y ago
  > But more to the point, 'vulns' seems like a very unnatural abbreviation. I would go with v11n (similar to i18n). Please no. I really don't like that convention and would rather you just type out the whole word if that's the alternative. Worse yet, for some reason you've decided to end in `n` rather than `y`. How can you dismiss the first four letters as an "unnatural" abbreviation, and then suggest inserting digits to represent the number of characters removed as an alternative? I'm not following that logic at all.
- JeremyBanks 8y ago
  Terms like i18n and l10n are bad for a11y.
  - reificator 8y ago
    > Terms like i18n and l10n are bad for a11y. Thank you for that, I am definitely stealing that phrasing.
- benatkin 8y ago
  Until now you apparently haven't been keeping a busy person typing in chat into account. Now you can. This use case isn't unique to the vuln/vulnerability abbreviation, but plenty of others. Including confusing ones like "i left you a vm" (virtual machine? where?).
- deleted 8y ago
  [deleted]
- munk-a 8y ago
  Oh please _please_ don't. i18n is a terribly obscure term with no implicit link to the actual word. This is a place where "naming things is hard" but for big concept chose short concise terminology while letting the details get lost in the verbose verbiage. Whenever I see i18n I just weep over the fact they didn't use the term "lang", internationalization is complicated and hard to shorten due to other meaningful jargon around it but there are better options than the dumpster fire which is i18n.
  - amake 8y ago
    > Whenever I see i18n I just weep over the fact they didn't use the term "lang" That's a bad idea because "lang" or "language" is already dangerously overloaded. People casually use it to mean any of (actual) language, locale (language + region (+ script, maybe)), script, or any combination of the above.
- deleted 8y ago
  [deleted]
warent 8y ago
4 sr i dt ths T (for some reason I doubt that's true)
- deoxxa 8y ago
  I read this as "for sure I do this too"
munk-a 8y ago
> Next time u c a shrt'd wrd u cn just ass. it's useful. B/c they r. They aren't always useful but I've rewritten your sentence in what I would consider a minimally legible format for me... but that's the problem it's for me. Don't introduce jargon in an effort to reduce comprehension time, it almost never works if you consider the time to familiarize yourself with the jargon. So when you're writing a blog post about PHP feel free to sprinkle in some comments about var vars, when you're communicating with your team use all your internal jargon... but when publishing an article for wide consumption just write everything out clearly.