I was thinking that maybe Apple had useful guidelines for how developers can prioritize their work. :)
I thought that too. I even thought of an explanation, involving tasks that impact multiple projects.
It's good practice to not editorialize the title when making a submission. You could misread many titles to mean something else, it's sort of a hidden assumption that you should read the article before commenting on it.
It doesn’t seem to me like the GP commented before looking at the article. I think it’s justified to clarify a title that’s prone to be misleading. That’s different from editorializing, which is inserting one’s own opinion or agenda in the title.
I actually thought you meant that this was about applying QoS algos to real life, before I saw the link lol.