How did they control for biases coming from parents? Research that I've read shows that gender stereotypes start to be instilled within the first few days after a child is born. Unless they're testing with children that have never seen a toy of any kind before, then the toy experiments are not detecting biological biases, they're picking up on a mix of inherited and learned responses. There's a lot of very bad science done to try to claim that there are things that girls like and things that boys like, ignoring the fact that the things that girls like vary wildly between countries and even over time in the same country (for example, blue was a girls' colour and ping a boys' colour in most of Europe until 1-2 centuries ago, and horses have swung between the two as a stereotypical interest several times).

So that's a target market of only 136 million?

Oh, and they're only concentrated in one of the wealthiest areas? Definitely not a problem then.

Blame posix for making all the goddamn pthread *_timedlock() calls take an absolute real time instead of a monotonic clock.

In anycase, I'm not even going to bother doing anything fancy. I'll let the system suddenly be one second off and then correct itself over the next hour. I'm certainly not going to do something stupid like letting the seconds field increment to 60. Having the ntp base time even go through these corrections is already dumb enough. Base time should be some absolute measure and leap seconds should just be adjusted after the fact in a manner similar to timezones.

-Matt

How times have changed. Someone posts and old copypasta troll and gets dozens of serious responses. If any post deserves a +5 Troll mod, it's this one. Beautifully done sir, though perhaps a sad reflection on what's left of this community.

It's not a problem for floating point, where division by zero is well defined (it's a NaN value). And division by almost-zero is not a problem in floating point either, though if you're going down one of the pipelines for dealing with subnormal values then be aware that it's likely 10-100 times slower than normal floating point calculations.

The only TRIM use I recommend is running on it on an entire partition, e.g. like the swap partition, at boot, or before initializing a new filesystem. And that's it. It's an EXTREMELY dangerous command which results in non-deterministic operation. Not only do SSDs have bugs in handling TRIM, but filesystem implementations almost certainly also have ordering and concurrency bugs in handling TRIM. It's the least well-tested part of the firmware and the least well-tested part of the filesystem implementation. And due to cache effects, it's almost impossible to test it in a deterministic manner.

You can get close to the same performance and life out of your SSD without using TRIM by doing two simple things. First, use a filesystem with at least a 4KB block size so the SSD doesn't have to write-combine stuff on 512-byte boundaries. Second, simply leave a part of the SSD unused. 5% is plenty. In fact, if you have swap space configured on your SSD, that's usually enough on its own (since swap is not usually filled up during normal operation), as long as you TRIM it on boot.

-Matt

It took a lot longer than a few weeks to break even for me, but it was less than a year. Allowing different thermostat settings at different times and on different days made the house quite a lot more efficient.

I'm surprised that it's taken this long. I've thought that MS and Apple should have been incorporating aggressive anti-tracking and ad blocking capabilities into IE and Safari for a few years, because neither company makes much money from ads, both could easily spin it as a user-centric decision, and it would hurt Google a lot.

The BIOS almost certainly won't enable any of the software-controlled power management features of your CPU. If it's a pre-EFI BIOS then it's also running in real mode and even if it's EFI it's likely to be running in a polling loop rather than relying on interrupts for user input.

I use the Mac equivalent, TextEdit, quite often for jotting down quick notes and for quickly opening text files (including rich text and Word docs where I don't really care about the formatting). TextEdit is a very thin wrapper around the NSTextView class, and so is the same sort of not-quite-demo-app as WordPad, which is a thin wrapper around Microsoft's rich text editor control. I have Word, Pages, OpenOffice and LibreOffice installed, but I probably use TextEdit more than all of them combined, because for most simple things it just gets out of the way.

Mozilla derives its income from things like search placement, which are paid proportionally to the number of users, so effectively anyone who uses Firefox and doesn't change the default search engine is a paying customer.

Open source, like proprietary software, is supposed to be about what the contributors want. In the proprietary COTS model, it's easy to identify the contributors: they're the ones handing over money in exchange for the product. In the bespoke model - proprietary or open - it's usually the person paying the developers salary. In the mass-market open source model, it's much harder (and may be a mixture of volunteer devs / doc writers / bug reporters and so on, as well as some people funding the project). For Mozilla, most of the work is done by people who are paid, but their salaries come from from an income stream (money from the default search provider and so on) that makes it quite difficult to see who the contributors are. Technically, they're probably the users, since that's essentially how Moz Corp gets its money, but via a lot of layers of indirection.

I mean, come on... just when the graphics performance starts to get good, people all want bigger displays which halves the performance and then want to go even BIGGER and halve it again.

My perfectly good Sandybridge i7 can't drive this shit. Time to rotate in another workstation. Again.

Grumble.

-Matt

Biking when it's snowy or icy isn't that dangerous, as long as your bike is in good condition and you've had a lot of practice cycling. I suspect that neither of these are entirely true for users of this scheme.

Keep burning them at current rates, and by 2100 we'll have run out. The headline really should have been 'Politicians promise their countries will do something that they'd have to do anyway, long after they'll have retired'