No argument there, but progress needs to happen somewhere. We'll all benefit from it in the long run.

The focus appears to be on the shader pipeline and raw polycount. Shadow sample sizes may not be their focus.

Even with 4 GPUs, this level of detail with realtime rendering is impressive. If you were bitching about non-realtime, I'd be on your side, but this is realtime.

It is designed such that this would never be an issue. Why? Because you have to skip several critical maintenance periods to hit it. Imagine if you, somehow, kept your car engine running for two years. Ignoring the logistics of this, doing so means you cannot have changed your oil etc.

Now, if it was on the order of 11 hours, that would be more of a concern.

... not when they would all have nearly the exact same runtime - they would all hit the failsafe at around the same time.

Not that this should ever happen in the air - as others have said, if the thing manages to run for this long, someone hasn't been doing maintenance.

Three. Carmack did the same, but he backed out I believe.

80 square meters is only a 30x30' square. It's not unreasonable that you had that space above your home...

It may have more to do with the people they are trying to train...

If what is done with the data as it streams to/from disk is the bottleneck, it doesn't matter if it's sitting in RAM for you before you need it, you'll still be bottlenecked.

Of course, if you're waiting for disk I/O then there will be a difference.

OK then, try a large tree or something that WON'T break. Because in that case, you eat the full force of it... with your nice and soft body.

Modern cars do get mangled easily, yes - the idea is that they absorb the impact energies instead of you.

OBDII is a diagnostics protocol, and whether or not the car's electronics supports it has nothing to do with what the electronics are actually doing.

Ancient sun hardware.

There may be a way to do so as it's running Solaris under the hood (getting to it is possible but comes with all sorts of "you are about to break warranties" types of warnings), but it's certainly not visible in the interface.

No, because the vendor appliance does not allow non-ssl connections. Neither can you supply your own certificate/CA data.

The set is not encoded in the universe, though the description of the set is. Else, every reference to "infinite" would, well, break the universe.

For a good long while it's been annoying when dealing with mangled SSL configurations - at least firefox let's you tweak stuff in about:config to work around them.

No, getting the site fixed is not always an option, and validation of the certificate is not always necessary. For instance, there was a good long while where Chrome was completely unusable with some of our ZFS storage appliances (which live on a nonrouted private management network) because of retarded cert validation changes. Sure, that makes sense when you are visiting your bank's site... but not so much when you're trying to get into something on 10.0.0.0/8 when you're directly connected to the thing with a crossover cable... and no, updating the software in the controller wasn't an option because of outstanding critical-level bugs.

Fun times.