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.
I assume you're not saying it is but I just wanna call out that zoning out behind the wheel isn't a good thing. Drivers should be attentive at all times regardless of whether the route is familiar. So maybe something is going wrong there, even if it's not trauma?
One can still drive attentively but be on a route so familiar that unless something unusual happens, the brain does not bother recording any specific memory of it.
Even at work, I can spend a week on developing something, implement it, and once it's done will have almost no memory of it a month later because it was just one more feature in a long series of features that are all pretty much the same.
The human brain is a filter that seeks novelty. All the repetitious junk gets compressed down to something like key frames. This is why things like alert fatigue are so dangerous. Any signal that only very occasionally means danger will eventually be ignored.
Is being compliance ablative armor uplifting, fulfilling work? Is there any way in which your personal competence and effort impacts whether the AI screws up or not? Do you have any way to build job security as ablative armor?
Fulfilling work disappeared a long time ago, the book bringing this up was from 2018 before chatbots were really a thing. We are just experiencing the acceleration to all jobs being bullshit jobs.
If screwing up gets me killed I want the person doing that job to be paid well and I want them to be held up to a high performance standard. I don't see how cutting pay for conductors is going to make anyone's lives better.
Or if we replace that well-compensated train conductor with automation I sure hope it's high quality stuff and not lowest-bidder slop.
> I don't see how cutting pay for conductors is going to make anyone's lives better
It's going to make passengers' lives better by making their train rides more affordable, allowing them to improve their lives by leveraging those funds.
Or, it's going to make shareholders' lives better by increasing their profits.
Either way, some people will benefit from it. The question is -- what is the real, practical tradeoff, and is the tradeoff worth it to the participants in the system.
Money, as a limited resource, means that money not spent on the conductor's wages can be spent elsewhere. In this hypothetical, fully automated trains can be run more frequently, so the money not spent on conductor wages means that the train comes every 5 minutes instead of every 15, and more stations.
It's going to make shareholder's lives better. And you better believe we're replacing conductors with lowest-bidder slop, that's the whole point. That's shareholder capitalism's playbook, it hasn't changed for the last 50 years.
What, you don't want to save a few bucks on a train ticket? Come on, you'll love it!
The classic HLSL compiler is infamous for being full of bugs (and slow, for that matter) so I wasn't surprised to see it come up here...
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?
hey! author here. I think I missed the opportunity to mention that, it wasn't only reproducible on the 40xx. it was my first hypothesis, but after I figured out it was a DirectX11 issue, i was able to reproduce on another windows machine with a different configuration. I just didn't have enough windows machines available to begin with. :)
AoT uses the same codegen (mostly) as the JIT so if you see a JIT improvement it's possible NativeAOT/ilc picked up that improvement too.
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.
You can always just not use OOP. C#'s tooling for functional programming and C-style programming is really good, thanks to stuff like statics on interfaces or spans.
reply