It's not about crypto, its about process. Compare this action to one by Debian or Wikipedia where there's a formal proposal, time for written pros and cons with convincing arguments for each side, and a meeting where the vote is held and impact to stakeholders is discussed.
You can't make large changes like this without undermining your viability as stable infrastructure.
I don't like crypto but this is poor reasoning, hastily implemented, and given very little time for discussion. There does not seem to be any concrete plan for notifying impacted projects or giving them a roadmap to migrate.
This is unprofessional and severely harms their credibility. It's not what was done but how they did it, and I don't doubt that subsequent policy changes can and will be implemented in the same manner unless it's addressed.
Their current product naming is still terrible.They went from the Xbox, to the Xbox 360, the Xbox One, Xbox One S, Xbox One X, Xbox Series S, and Xbox Series X.
You don't need a grid forming inverter to re-synchronize with the grid, you only need a grid forming inverter if you need a complete cold start or to support a grid island.
In the context of our discussion, adding more capacity, that's exactly what's needed here. We're not replacing 100% of energy sources with solar, we are replacing energy sources with _renewables_ which is hydro, solar, wind, arguably nuclear as well.
Even extending your argument to "well we need to only have solar" then you need a grid forming inverter with batteries. That's not a massive increase in complexity or time and supports the "just tie them to the grid" statement.
I mean normally this type of discussion is silly, but in playing competitive shooters latency does make a huge difference, and it shows that XWayland is adding ~4ms of latency.
There is a native Wayland driver for Wine/Proton but it's enabled through an environment variable, not by default. This will probably be default in Wine 12/Proton 12 because Valve wants to squeeze as much performance out of SteamOS as possible. The gaming mode UI runs under Valve's own Wayland compositor (gamescope) already, but games are currently in nested XWayland windows.
A lot of the EKS disadvantages, I've noticed, are from AWS attempting to make things complicated. On the GKE side it's really set and forget, just pick a release channel to subscribe to.
AWS makes you do things like manage node OS and addon versions, which is pretty ridiculous. I feel like it only exists to lock people in to ECS/Fargate and make people assume Kubernetes has to be complicated.
I am not a graphics engineer so I hope someone corrects me, but my understanding is that Unreal uses a deferred rendering pipeline to handle complex lighting, and deferred renderers only work with temporal anti-aliasing.
The FSR/DLSS upscalers are typically superior to TSAA and are a reasonable replacement.
I turn on my PS5 controller and it turns on my entertainment system and my game is right where I left off. All the games and the OS get silently patched while the machine is in "rest mode" too.
Steam Big Picture means I get to deal with launchers, games without a gamepad UI or designed for TV viewing, Windows Update (or on Linux, incompatibility), shader compilation, etc.
I don't see PCs replacing consoles any time soon, when I'm done working I don't want to deal with any of that stuff. I respect that some people do but that is "brain goes off" time for me.
Steam only exists because Valve forced players to install it, force an online activation, and permanently bind their retail copies of Half-Life 2 to a Steam account. They also forced patching which meant in an era of dialup you couldn't play your single player game for hours, and needed to be connected every 30 days or your game would stop working.
None of the console manufacturers pulled that shit, that Valve gets a pass is wild to me.