Honest question. Everyone are using rightclick, so when the ½ second delay still hasn't been reported on github, I would assume that it doesn't really bother people all that much. Which would be odd, since it feels like a big annoyance to me! So, what's your take? Have you noticed it? If so, is it a big deal or no?
I remember a talk on youtube where someone talked about a similar delay in the latest version of Adobe Bridge. He pointed out that there were nothing whatsoever that warranted that a never version suddenly performed the same task as before noticeable slower. More importantly, he managed to put into word exactly why this delay was a big deal. I wish I had bookmarked it. Because I have a hard time putting into words why exactly it matters. But I think I'll try:
When I code, I typically hold a lot of different stuff in my mind. I have an overall goal I'm working towards, like adding gamification, and in order to do that I need to create this function, inside which I need this relatively simple algoritm, which I copypaste from something else and then edit a bit. Now, when I rightclick, I notice the ½ second delay and It distracts me. Normally, rightclicking and seeing the rightclick-menu is mentally throught of as one single action. Cause and effect are intermingled, just like when you throw a ball. The ball flying through the air is a part of you throwing it.
Mentally , there is a lot of difference between something being instant, and having a delay. In most of our interaction with a computer, we are blissfully unaware of the distance. As I type this, I consider how it would be smartest to phrase it and such, but I don't really think about the physical process of me pressing down a key, the software registering it, the screen updating, and said character appearing on the monitor. We have this flow where cause is in the background and we only experience the effect. Same with rightclick. I rightclick and select "Go to Tag Definition". It is a single, quick action, which doesn't disrupt my flow.
