Researchers say? Really? No clue as to where they are from or what they have been trained to do? Because it is sure as hell not anything that uses carbon dating.

Yes the article gives some caveats but it really isn't enough. C14 dating really, really isn't as simple as it looks. As an archaeological scientist (well I trained as one) the one thing that was drummed into our heads was that C14 cannot be accuratly used past 1950 and that C14 dating is a science based upon statistics and will never, ever give you one year as an answer.

The reason C14 can't be used past 1950 is that the whole thing is based upon the idea that in the past the amount of atmospheric C14 has always been the same as in 1950. We know this isn't true however. Since 1950 nuclear testing has really screwed with the amount of C14 in the atmosphere and we know that in the past C14 varied as we have ways of checking (this is mostly done by counting tree rings, I know high tech).

So we have adjust the results we get based upon what we know about the amount of C14 in the atmosphere. I'm going off track here so I'll just point you in the direction of a website that shows how C14 dates are calibrated. http://c14.arch.ox.ac.uk/embed.php?File=calibration.html#calibration

The main reason that this research is suspect is that C14 really isn't suited to this sort of fine detail work. I'm sure that you can date wine but the result you would get would be pointless. You could probably get a 95% certainty of the wine coming from a certain date range but that range would be so wide as to be of no use. If you want to get a precise date then you can but only by dropping your certainty to an amount to low to have any confidence in. Your magin for error would be astronomical.

I never thought I'd say it but who approves these non-articles to appear on /.?

Oh, I'm not, other people are. Like the guys who work for SUN, who integrated the best available multi-threading library for Java into the standard libraries. This was like... many years ago.

Keeping in mind that C# and Java are virtually identical, why the hell wouldn't Microsoft implement a library that is "as good, or better"? Why would they implement some toy library that can't handle even trivial scenarios, let alone scale to hundreds of cores or handle huge enterprise apps?

The only reason I can think of that they wouldn't do things well is that they... can't.

When was the last time you bought a car that wasn't manufactured in the U.S.?

I seem to recall companies like Honda - companies that are not U.S. based, mind you - building factories in America because, well, cars are friggin' huge. It's expensive as hell to ship them across an entire fucking Ocean and then drive them cross-country. It's cheaper to pay good wages in America than to pay lesser wages in other countries and ship it out.

Yeah, yeah, there's still plenty of companies that import, but as stuff like Chrysler and whatnot collapse I'm sure that there will be foreign companies looking to snap up fully-functional plants so they can save on shipping. Remember, having a plant in the states gives you access to most of North America by land.

Ok. It's my turn to do this. At least one person has to everytime Opera comes up here. Opera is free. It has been for years. No fees, no adverts, free.

Is that what people want?

And from earlier

But it's this, is it? No enigma... no dignity, nothing classical or poetic... only this... a comic pornographer and a rabble of prostitutes.