They're being soft is both the cause and effect of not being able to see that porn?

For some, it wouldn't be the first time protection had been breached.

It's the FoodBabification of science.

We'd better nuke Mars and destroy all the data from and engineering advances that left to the Rover just to be safe.

www.cups.org top-of-page for me has links/dropdown-menus/etc as follows: CUPS.org Login Blog Bugs Help Lists [gap] [Searchbox] It's as if someone at some major computer company didn't think about portability among browsers (or smaller displays, or whatever other assumption they made) that causes that other link not to appear (or render off-screen or be hidden behind some other element)

All the links are to blogs and release-notes, but none of them (nor anywhere obvious on cups.org itself) actually has a download or instructions where to get it. New release sounds nice. Not usable if we can't get it, but "sounds nice", so at least it has that going for it.

Who decided to use a hexadecimal multiplication table as the lead image for a story about base-10 multiplication tables?

Monitoring about 56% more students costs 8x as much? Gotta love no-bid contracts.

It suggests that the company executive's statement about iPhone and Android consumer opinion is a known premise upon which he predicts Nokia will build. But that consumer opinion *itself* is (according to the article) the novel reported idea and this same exec's opnion too. He's not just filling a niche, but claiming the niche even exists.

Very...slowly...

Er, the whole point of each of those package-managers dragging in a whole stack of stuff is to avoid the whole "one manager/upgrader stomped another's files" problem that got this whole thread started. Fink and MacPorts each have their own (for example) libxml2 so that neither one's nor apple's feature-enable/disable, interface-compatibility, or other changes affects anything except its own packages, which presumably know how their own lib is built. If CPAN had behaved the same way, we wouldn't be here, because apple would know exactly how its versions of things were and its upgrades would be self-consistent, and user-installed versions *somewhere else* would not be touched and would remain self-consistent with themselves. That's really the only solution that's easy to make work well (or at all) as a few-parentlevels-up notes, and that's precisely what you criticize Fink/MacPorts for doing. If you build from source yourself, you're using apple's versions of libs, which is fine as long as you trust apple not to change things like this. If you do so and keep your files in /usr/local like you're supposed to, at worst, you'll have to recompile when an OS lib changes. The problem here is when users *didn't* restrict locally-installed things to /usr/local, which is just silly.

The only time I see blue is when I use Winders also, but it's unrelated to my desktop-pattern...