A new coinage that I noticed in the past year that also grates on my ears: "learning" as a substitute for "lesson", as in "what were your learnings from the hackathon?" Anyone else caught this one?
This is by far my favourite post in this entire thread -- I don't think I've ever seen Seymour Cray referenced as an authority in this manner before :)
Not specifically to OP, but for everyone unhappy about the use of performant: Pretty happy to concede that it isn't our finest bit of writing. Pretentiousness? Lack of technical nous? A bit of hurried/careless wording? I'll let you folks decide...
(1) It's not perfectly clear what the definition is in this particular context. Usually the word is used to indicate "our stuff is rad fast bro" implying that speed is obtained through cleverness such as the use of efficient code or an efficiently scalable architecture, but the linked article violates this definition by comparing apples (CPUs) and oranges (storage). It's nonsensical in the manner of "my word processor is more performant than my fractal renderer".
(2) Normally, use of this neologism saves time by replacing a long phrase. This use in the linked article is backwards: the word "faster" could have been used in place of the longer "more performant."
utilise namespace std;
whilst (performant()) {
pontificate();
}
Edit: bonus `problematic` operator for exceptions.Whilst implies parallelism/concurrency, it's not the same thing as while.
Problematic is more a tumblrism than anything else.
Also "utilize" is more specific than "use": it implies "using for a desirable purpose". Consider:
(1) This daemon process is utilizing all the available bandwidth.
(2) This daemon process is using all the available bandwidth.
Sometimes people making up new words do come across as lazy, but you can easily go too far in the other direction, too.
What's the difference between speed and performance here?
(2) The bandwidth is being entirely consumed, but it might only be because the process is misbehaving and consuming more bandwidth than necessary.
Speed only translates to performance if the resource being quickly consumed is actually needed. Example-- a game might always use all CPU cycles, but only when rendering the most challenging scene is reaching peak performance.
For your game example, I don't see what isn't encompassed by "speed" (how many FPS you get out) or "efficiency" (how much CPU/GPU you use to do it).
I suppose you could say that someone using just about any of those words is trying to sound smart or overly formal, and so we should deny their status as words to bring the speakers down a notch.