I Googled Mozilla Thunderbird and the first hit was the download page, using HTTPS. You're right SSL isn't enforced, but that's a chicken and egg problem for Firefox downloads I guess, now that TLS 1.2 is enforced and the user may be stuck with a browser not supporting that.
SSL 3 is still fine for protecting integrity, just not confidentiality, so it is okay for downloads.
What use is having HTTPS to protect the very thing that you need to implement it. It's a basic chicken and egg problem, replayed every time OpenSSL gets compromised, and successfully circumvented by securing it with something else.
Think about it: there's an SSL break and you need to update OpenSSL. What good does it do you to have it available over SSL?
Not that people shouldn't be using GPG, but only using it means you only protect the paranoid.
http://www.stroustrup.com/bs_faq.html#bootstrapping
However, the first C compiler was not written in C, but in NB, an intermediate step from B to C:
http://stackoverflow.com/questions/18125490/how-was-the-firs...
But anyway, the comparison isn't very good because haskell/gcc don't develop sudden security vulnerabilities that instantly turn existing binaries unusable for getting new ones.
You can't get it over SSL. Not to worry, the binary will be signed by Mozilla right? Yeah, GPG only. Not x.509 signed.
But hey, the online install page supplies it over SSL right? Well, sometimes. But it turns out they don't enforce SSL use. Cue SSLstrip.
PS On MacOS X 10.9 Apple by default prevents running unsigned binaries. Not to worry, Mozilla tells you how to bypass the check, not even hinting it has a very valid purpose. https://support.mozilla.org/en-US/kb/firefox-cant-be-opened-...