Ah, the flames from someone without much finesse: Premature declaration of failure to discourage further examination ("The masses have spoken..."), misidentification of fault ("If Apple could have continued using gcc...", "[The FSF] should have gone into the hardware business..."), citing trends with no backing and overvaluing business interests ("...then corporations wouldn't have run away from any GPLv3 software..."), and outright lying about intention and execution ("...weighing the costs of the walled garden (censorship etc) vs the benefits (no viruses)...", "...the attempt to take over the Linux kernel by renaming GNU/Linux..."), your post has so much flamebait to choose from it's almost as if you were taking instruction from an open source proponent who is eager to convince licensors to pick non-copylefted software licenses so they see their work become charitable contributions to software proprietors.
If there's so little interest in protecting oneself from international spying, malware, and other forms of user abuse Glenn Greenwald and other journalists would find it hard to get articles on the Snowden revelations published anywhere, world leaders wouldn't be holding meetings about the Snowden revelations, and people/organizations around the world wouldn't care about encryption. Don't confuse a non-technical user's inability to do better than running proprietary apps from a walled garden with not caring about these issues. They get both no software freedom and plenty of malware in their choice. Most computer users are weighing options where freedom is not available; they're suffering from the myth of choice where all of the readily-available options they know about deny them loyal computers.
Speaking of proprietors, Apple is no victim here. Apple wasn't forced to switch to LLVM and Clang, they chose to because they're proprietors eager to rob users of their software freedom in derivative works. If any organization with the means can be accurately accused of not writing their own stuff, it's Apple not writing their own compilers but instead relying on other compilers. This goes back to NeXT which was the first big GPL copyright infringement case (according to Brad Kuhn, former Executive Director of the FSF which holds the copyright on GCC in his discussion on his OggCast "Free as in Freedom"). NeXT got caught distributing a proprietary derivative of GCC which contained code to compile Objective-C. When Jobs spoke with the FSF about the matter, the FSF informed him that they would enforce their license (GPLv2). Jobs never liked that and never forgot. Apple doesn't mind the GPL they just don't like to be in a position of equality with their users unless they can pull out of that relationship when it suits them (see Apple's purchase of Easy SW which originally developed CUPS).
The FSF never tried to "take over the Linux kernel" and isn't doing so now by properly identifying Linux as a part of an operating system. They have said for years and continue to say they would like the GNU Project to get a share of the credit (1, 2). They also acknowledge that there are systems that don't include GNU and therefore should not be called "GNU slash" anything. No doubt, it would be equally unfair and erroneous to call GNU/kFreeBSD or GNU/HURD a "Linux" system when Linux isn't a part of that. This has nothing to do with capability of writing a kernel; a Linux kernel without the blobs is available so there's no pressing need for a fully-free system to have its own original kernel written by the FSF or the GNU Project. The core of the issue was and is a "greenwashing" (as Brad Kuhn aptly put it) open source movement not bringing to mind a user's software freedom (mirror) and the intended effect (older essay, newer essay) that has on people not understanding what software freedom is for its own sake.