I think the average player would not appreciate hourly crashes, especially in games without aggressive autosave - that potentially means having to replay 10+ minutes worth of gameplay on a regular basis because your timing was bad, when you consider how a typical game is built. You could compensate for this in some game types I guess, like in a competitive FPS you'd restart the client software between matches and hope a match never lasts long enough to crash. But that's no substitute for real robustness, IMO.

1. A lot of single family dwellings are occupied by renters. In this scenario, the renter has no ability to install rooftop solar, and the owner has no incentive to install rooftop solar because the renter is paying the energy bills. (The same goes for things like installing high-efficiency heat pumps etc.)

2. HOA regulations can block things like rooftop solar depending on where you live.

3. The up-front investment involved in rooftop solar can be prohibitive for many people. Things like tax incentives can help but we've been getting rid of those under the current administration, and tax incentives only go so far if your tax return is 6+ months away.

That sounds miserable.

Or if we replace that well-compensated train conductor with automation I sure hope it's high quality stuff and not lowest-bidder slop.

Comments URL: https://news.ycombinator.com/item?id=49757081

Points: 2

# Comments: 0

Fantastic seeing the author lay out all the steps involved in getting a renderdoc capture of a browser and what's involved in debugging shader issues in a webpage.

It's interesting that the issue only manifested on the geforce 40xx if it was an fxc issue though... wonder if it's fxc combined with a driver issue and not just one or the other?

Unless it's a runtime-only optimization, like guarded devirtualization... there's no straightforward way for an AOT compiler to do that without profiling data.