In case you don't get it Predator . This video is not about doing the greatest CG. It's kind of obvious that the distortion was on purpose.

I mean, shouldn't anybody reading /. have a disaster safe backup? At least at a different geographic location?

exactly

The current terms of service (which you accept when you get this thing) are that the program is safe by definition. The user has to keep the pc free of viruses. Zerodays are the users fault as well, what so ever.
Which basically means, when ever somebody does something bad with your id, the damage is yours.
They even read, that you should only keep it on the card reader for the few seconds of usage.
As if those few seconds are not enough for an attack. One thing that already works easily with an exploited pc is remotely changing the useres pin, without him knowing. Well....this already is a damage for the user of a couple euro + time loss because you have to go to the local citizen center. (can anybody thinks of a nice DOS attack on the city centers)

This is not a bug, it's a feature.
Now they can upload their spying tool to everybody without a warrant. All they need to do is accidentally mixup the new release of the passportapp with the trojan.

Oh cool. I've got one too. Together we could build a dual band computer. This hast to be way more powerful.

mod parent up please

What would really interests me more is, if it has a suitable performance.
Right now I only use flash, if my room temperature drops to low.

From what I heard. Raytracing scales better than rasteriastion. In other words O(raytracing) \subset O(rasterisation). Obviously, raytracing has really bad coefficients.

The Problem with Wine is, that from the user point of view, it is extremely unstable. It tried it out a couple time with games that had Gold or Silver status. None of them worked with the version I tried.
I think I would be really worth it, to stop developing more features for a while and add as many regression tests as possible to the project. So that the project gains stability. Since in the end, the real success is always determined by the end user.

I take it, that you don't get the big O notation correct. As the constants are different, it makes no sense to calculate when nlog(n) < n.

Ask yourself, when is C*n*log(n) < K*n, for unknown C and K(these constants depend on the implementation) and you will see that the only way to determine this is measuring the result of your implementation.