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.
(for some reason I doubt that's true)
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.
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.
Thank you for that, I am definitely stealing that phrasing.
You won't see me using it in an email or other long form writing though.