Look at the Guardian link I provided. Many of your comments and questions are answered there. It looks at how the degree of austerity measures has affected the rate of recovery for various countries.

Remember, not all public servants are equal. Privatization will cut the count of "public servants", but can actually increase the cost of the service for a net loss to the economy.

Actually, once they have once and for all ceased even trying to pay back the loans, they will be running at a surplus. A bit of currency devaluation will be a boon to their significant tourist trade.

I'm not claiming it is the best possible solution, but since the IMF et. al. won't quit flogging the dead horse that is austerity, it may be the only option open to Greece.

THIS! Mod up!

Don't forget visual impairment. They may be depending on the splat looking thing next to the red thing being the send button. Move it and good luck.

What happened is that people who used the system very day, day in and day out, became so fast at entering the machine settings the rate of UI events exceeded the ability of the custom monitor software written for the machine to respond correctly to them.

Which is still to some extent a UI issue.

But the literal "killer" is what happened next:
  1) The machine detected that it had screwed up.
  2) But the UI reported this by a cryptic error message: "MALFUNCTION nn" - where the 1 = nn = 64 error codes not only weren't explanatory, but weren't even included in the manual.
  3) And if the operator hit "P" (for "proceed") the machine would GO AHEAD AND OPERATE in the known-to-be-broken mode, giving the patient a fatal (high-power, not-swept-around) electrons rather than a 100x weaker flood of x-rays, with NO FURTHER INDICATION that something is still wrong (unless you count the patient sometimes screaming and running out of the room.)

If 2) and 3) aren't user interface problems, what is?

Well that may be so. But as you get older you get less patient with people wasting your time.

Let's say you're 90 years old. You're using a webmail system which does everything you need it to do. Then some manager has a brainwave and suddenly all the functions are somewhere else. How much of the 3.99 years the actuarial tables say you've got left do you want to spend dealing with that?

It's not just 90 year-olds. Take a poll of working-age users and find out how many like the MS Office Ribbon; how many people are cool with the regular UI reshuffling that takes place in Windows just to prove you're paying your upgrade fee for software that's "new"?

Reddit was started as an experiment in free speech.

Wait, what?

I recall Alex coming on Slashdot a lot to promote Reddit when he first launched it. "An experiment in free speech" was not anything I recall being discussed. I also remember him posting on Slashdot while still developing reddit.

What I recall, is promotion of a general interest platform that was more open than Slashdot (unlimited moderations for all!) and less susceptible to vote brigading than Digg.

It was while ago, so I may be a bit foggy on the specifics.

According to wikipedia, that had software problems that ended up killing people What's that got to do with UI changes and user experience?

The original post was about bad user interfaces causing harm to people. Changes breaking the user experience was only one of the issues.

In Therac's case the bug WAS primarily in the user interface:
  - Due to a race condition, if a button happened to be pressed at the wrong moment and the menu filled out in a particular order, the device would configure the electron beam for x-ray generation rather than electron beam generation (high electron beam current, no scanning) but not position the target, flattening filter, collimator, or ion-chamber x-ray sensor in the beamway, resulting in a configuration that irradiated the patient with beta radiation, rather than x-rays, at 100x a normal dose.)
  - The machine DID detect that there was a problem. But it reported it as "MALFUNCTION nn" - where nn was a number from 1 to 64 and not explained in the manual. If the operator entered "P" (proceed), it would then go ahead and operate in the improper mode anyhow.

Both the second part and most of the first part sound like user interface problem to me.

I was working as a developer when the news of the Therac 25 problems broke, so I remember it well. You actually have it backwards; it wasn't bad UI design at all.

The thing is mere functional testing of the user interface would not have revealed the flaw in the system. What happened is that people who used the system very day, day in and day out, became so fast at entering the machine settings the rate of UI events exceeded the ability of the custom monitor software written for the machine to respond correctly to them.

If the UI was bad from a design standpoint the fundamental system engineering flaws of the system might never have been revealed.

I think what the Libertarians fail to realize is that farmers, as a general rule, are not smart enough to diversify or maintain course.

First, I think that's a ridiculous assertion. Smart farmers don't diversify because the taxpayers bear the risk of their crop failure, or of crashing prices; they have insufficient incentive to diversify.

Second, if we had a true free market, dumb farmers would go out of business and we would be left with smart farmers allocating resources efficiently. Isn't that the point of economic libertarianism?

Note: I am far from libertarian.

Someone started uploading all the HackingTeam source code to GitHub ... There are also some signing keys for kernel drivers in here.

IMHO:

Anyone with a project hosted on git hub should pull a backup copy NOW!

Hosting this leak on git hub could lead to moves by authorities to contain it - which could have the side effect of making GitHub and/or some projects on it unavailable - temporarily or permanently.

Better safe than sorry.

... will this help bona fide security researchers with their work on fighting exploits on all platforms ... ?

I wonder if this will also help people trying to write open software for closed devices? Signing keys, driver sources with spyware installed, ... Not only does it expose the malware bypassing the user's security, it may also expose the internal details of how the devices are driven and/or how to compromise the malware's and devices' anti-user "security".

(I have often wondered how many of the closed-driver devices have the code closed just for business reasons and how many are closed because that's where the spyware has been installed and they can't let the source out - even sanitized - because that would lead to the spyware's exposure.)

What do you mean by cyclical? Do you mean the livestock/fertilizer/crop/fodder cycle? Do you mean crop rotation? Or something else entirely?

Just curious, since I'm not aware of either cyclical production or crop rotation being a requirement for organic farming (although both are considered best practices).

The goal is to intimidate the makers of such designs. Arrest first and ask questions later, when such designs get out.

It's also to make it harder for "the common man" to arm himself - in case a Schelling Point is reached and a LOT of people suddenly decide that they need to arm themselves against the government or its puppeteers. By slowing them down, and reducing the number and quality of designs available, the powers that be have more time to react and try to divide and reconquer.

Of course intimidating designers is a big part of that.

This is not the first time they did this. In fact it has quite an interesting history in cryptography that was classified as a munition for just this reason.

Which is why OpenBSD is hosted from outside the US. (It's NOT just that Theo happens to live in Canada.)