> the idea that developers for enterprise systems with deployment tiers (dev, test, UAT, prod) should not have direct, full-time access to prod sparked heated debate.

I do not want direct Prod access. Thatâ(TM)s too much liability for my tastes. Iâ(TM)m a developer. Iâ(TM)d much rather go through the once or twice a year hassle of working through someone with access, rather than let the Prod databases be compromised because I had an off day and fell victim to some 0-day or social engineering.

I've worked rather extensively with a Xerox DocuColor 252 over the last four years. Those yellow dots are anything but microscopic. I could plainly see the dots on most printouts under standard office-style fluorescent lighting. They always bugged the crap out of me.

Why test EVERY combination of plane and gadget?

It is impractical for pharmaceutical companies to test compounds on every combination of person and condition. Instead they perform tests on representative samples of people.

Fixed that for you. The whole idea of appointing a judge for life is to help ensure impartiality. They don't have to fear losing their job for making an unpopular decision.

Retracted. I must learn to read more carefully.

TFA doesn't mention a source, and that bothers me. Is this information about Lion derived from the early developer test versions, or has someone at Apple stated that this is the way it is?

Yes, I was noticing that. Very obviously a loop.

Why does it have to be implemented before it can become a finalized specification?

I'm afraid I don't understand what your point is. Do you mean "working out" as in exercising or as in working out the details?

By what you're saying, I should infer that the writers of the HTML5 recommendation are creating the documentation to fit the existing browser implementations of HTML5? What does time to implement have to do with the writing of the recommendation? W3C writes the recommendation, and browser developers implement the recommendation in their software--that's how it (should) works.

What we need is "a day in the life of a W3C draft" article to figure out why these standards and recommendations take so long to mature.

The "WebP" versions may look murkier because whoever made those images forgot to add a colorspace profile to the PNG images (or, alternatively, remove the colorspace profile from the JPEG images).

With tools like that, do we really need math classes?