I still wonder why some guys are thinking on here that loss of a GS signal automatically equals a crashed airplane?

It's a technique, and one that works just as well as going around. Either one can be safe or unsafe, circumstances dependant.
I think that the potential for confusion over approach minimums in these circumstances puts you at greater risk for a CFIT accident - especially in an automated airplane or an airplane with more than one crewmember or both particularly in mountainous or urban terrain - or especially over featureless snow covered terrain where you break out right at mins. Hand flying on steam gauges is one thing, but reprogramming an altitude pre-select, or reconfiguring the autopilot if it hasn't already clicked off or some other cockpit duty that could distract you when you should just click everything off and hand fly is something that could consume time at the wrong time. Additionally, if you're crewed, you've got to explain what you're doing to the other crew member, even if you've briefed it. Then what if his glideslope didn't fail? Do you swap PF-PNF duties so you can complete the approach? It's not that confusing a maneuver, but I suspect you are aware that when something fails -especially an instrument, it is rare that you recognize what happened immediately, or that your brain doesn't take time to process something. I've seen guys miss a "nav flag" entirely and try to fly an approach that wasn't even there, or other stupid - yet easy to make - mistakes.
My "dumbest" instrument failure related mistake was on an ILS as an FO about 6 years ago. I was flying the approach, inside the marker when my airspeed started to gradually slow. I kept adding added a little power figuring it was the ice we'd been accruing on the descent, I pushed the power up a little more, then a little more and then the captain says, "hey, why are we going so fast?" Well, my cross check hadn't included the captain side airspeed or the GPS (which was not conveniently located for me to look at), and the heating element had slowly failed on the descent and the tip of the pitot tube on my side froze over without covering the drain hole. At this point I looked over and was at about 1000' doing about 180KIAS on an approach that was probably going to be close to mins. The captain said, "no worries, just go off my side and go to flight idle, this'll work out." In a big turboprop it worked out, and we were able to restabilize our airspeed at about 400' to break out at 300-ish. That said, both my failure to cross check properly ( should have immediately picked up the fact that the rate of descent was picking up irregardless of the captains airspeed and GPS), and the captains attempt to salvage the approach were inappropriate responses. It would have taken 5 minutes to come back around and do it over, and we would have gone through 1000' stabilized on speed with the airplane configured appropriately and wouldn't have had to do anything aggressive. That said, it took me probably 10 seconds for me to think, "wait a sec, this isn't right, why am I so slow I've got power pushed up, gear is out, but it shouldn't slow me down, we're not getting that much ice." The CA caught it, and I only had about 600hrs at the time, so really, inexperience is what that was all about, but seriously since I started flying SPIFR the wisest words I've heard spoken to me yet have been, "if you ever find yourself saying,
I can make this work, then you're doing it wrong."