I wonder why GitHub has this spinny waiting screen whenever I fork a repo.
Forking is a pretty fast action, and there's no obvious reason the page couldn't poll the server a little faster to find out if it had complete. Certainly, I'm going to click the "refresh" button that they provide much sooner than they currently poll -- and every time, the fork is already complete.
Why make people wait?
Follow
@varx A better question is, "Why use #MicrosoftGitHub?"
@lwriemen I mean sure, but the question remains—someone made a UI decision, and I'm curious about it.