Much of the unsigned software is perfectly useful valid stuff, much of it safe, much of it open source but that action to run downloaded code puts a lot of trust in the developer and the source. Even run as a non-root user it can still do things that cause real problems including steal confidential information.
People who don't want/like the walled garden can disable it trivially from the settings. For people like my mom, who clicks on any ad/link/attachment without a second thought, this will save a ton of headaches.
None of the devs has an Apple Developer account and not one of them, understandably, is prepared to churn out the 99 USD just to be able to sign the OS X flavor of their app: http://goo.gl/gzFZO
Shouldn't a kick-ass app like Darktable be easily deployable by anyone, not just those who know how to circumvent the 'walled garden'?
Reading the link, it seems like (some of) the devs have philosophical objections to doing that; fine. But philosophical objections aren't the same as "it can't be done".
I don't necessarily disagree (I have a mom too ;)), but: (1) there are many trustable open source programs that are unsigned because their developers cannot afford or do not want to pay $99 per year for an Apple developer account; (2) OS X could display a warning that the user can override.
What happens now is that people will Google for the error to install some legitimate software, find a blog post that describes how to disable Gatekeeper, and switch of Gatekeeper permanently.
If it had an overridable dialog straight from double-click, people will just see this as an annoyance and end up clicking the "Yeah, whatever!" button without skipping a beat.
The way it is, it's actually overridable per application with "right click->open" which gives you the overridable warning you wish for, with OSX actually remembering the overriding and you can subsequently double-click on the now whitelisted app. This whitelisting apparently survives even Sparkle updating.
It appears that it's just convoluted enough for people dangerous to themselves not to shoot themselves in the foot, yet convenient enough for the informed user to act easily. And ironically the solution is actually written in the non-overridable dialog, yet the kind of people not reading dialogs is precisely the risky kind. I'd venture it's made so on purpose.
As I said in my original comment ;).
This whitelisting apparently survives even Sparkle updating.
Sparkle probably never sets the com.apple.quarantine attribute and if the application does not have LSFileQuarantineEnabled set in its Info.plist, its downloaded files are not put in quarantaine. Applications that do not have that extended attribute are never checked.