As you’ll see later in this reply, I actually think it is instrumental - it is a form of communication. But that is OK. You’re busy (aren’t we all?), so not all links can be followed (:
Sure, and that is how we work mostly. We also think that it should be possible to have this rendering stuff all implemented in such a way that a user doesn’t have to think much. Obviously we aren’t there yet.
But perhaps you might be able to understand that getting there is an evolutionary process. In a perfect world where Rhino already were perfect, all hardware we started out with were perfect, all operating systems were perfect, all drivers were perfect my initial Proof of Concept implementation for @andy back in 2013 would’ve been also just that - perfect. But none of the parts involved are perfect, so it will be an on-going struggle to get there. The same is true for anything, really. The world isn’t perfect, we all - you, me, anybody else - are working on improving it, be it door knobs or software.
I fully understand, and I can’t repeat it enough: we’re working on it. We believe we can get this to work without even a genius menu like that (ergo eventually out-doing that genius menu). Unfortunately you’ll have to probably either use the Raytraced mode in a smaller viewport, tweak settings for now, or just not use it and every now and then see if I have succeeded any better in the future. This is how I do it with Microsoft Windows Update.
I get super annoyed by the automagic updates Microsoft wants to force on me with Windows 10. That’s why I completely disabled the update service, and will run it at when I am ready for it. Only 12 hours of active time? That’s crap. I have my software running 24/7 and I am not going to be told when I can’t and cannot be active. I’ll turn it on when I find it does the things I want it to do in the way I want it to do. (And yes, I have sent in several items of feedback regarding this matter, read on… 
).
–
The article by Mr. Cooper is an interesting read, and no doubt there are valid points. But did Mr. Cooper also tell his findings directly to the creators of the software? If not, then writing a ranting blog-post is a futile exercise in wasting energy. Nowhere in his blog-post does he tell he tried hard to communicate the flaw he identified. Ensuring creators can improve their product the design process needs communication. Fortunately we have that here in the form of this Discourse forum. A place where I as a creator can solicit feedback from you the user. Assuming that someone will search for random blog-posts to find feedback about the software they created is just utterly stupid. Lucky me I got linked to it (and lucky for you I took the time to read it 
).
On point three, I think users should investigate and think for themselves as well when acquiring peripherals. No one in their right mind is going to expect a moped to go as fast with four persons (4k screen) crammed on it as with only the one on it (regular Full HD). (I know you said humans don’t care, but they should still be reasonable).
Anyway, thanks again for your write up.
Back to improving the world, bit by bit.
Cheers,
/Nathan