I wonder that people actually object to offering an executable which is an installer for download. When, at the same time, mainstream companies like Adobe and even FOSS portals like Sourceforge not only do the same, but even worse.
They distribute executables that will download content from untrusted sources without any possibility to verify or control what is being downloaded, and they use drive-by installs (mostly McAfee or Ask) to which the user "consents" by not reading the small print. But... that's OK.
This is a solution to prevent future browser warnings though. If you have an installer that doesn't change often that downloads an executable and runs it, you don't get the warning for the installer once it's been around long enough, and future patches are handled outside of the browser to avoid browser warnings.