I see it now, getting bought by Disney, fire everyone except those keeping the servers alive, add marketing.

They can help in prosecuting offenders, and in that way be part of a deterrent that improves security. If security is measured in a way such as (average leak size/mean time between leaks)

Mind if i put that piece of gold into my '.fortunes' ?

Sure, go for it.

Not yet.

No. Down the line, maybe a cap on the very top end (tens of millions of pageviews per month) -- if that becomes a problem (it hasn't yet).

But we have absolutely no problem serving high traffic sites (millions of pageviews per month) for free, it hardly costs us a thing.

It falls so far outside of day to day programming, that it feels somewhat alien.

I however miss the argument a bit, as i can imagine a mechanical transform that can turn the premature exit version into one without. (using if statements to remove all operations until the end of the loop)

I agree that it's pretty easy to transform the code. You could also take the code block in the loop, make it a separate function, and return instead of break. It's no harder to understand a block with break statements than it is to understand a function with multiple returns, although maybe Dijkstra wasn't a big fan of multiple returns, either.

Good thinking on both counts. Multiple returns are another limited form of exceptions, and you don't need to go back in time to ask the Dijkstra from that period if he disliked them. They too escaped theoretical treatment as it was formulated at that time :)

I have put some example rules to introduce exceptions in Hoare logic at http://snipt.org/lWg (I needed monospaced fonts, sorry for the inconvenience)