More precisely: not very random tries.

Once silicon is in control (which is where responding grid requests to delay consumption is more or less necessarily heading) you could even achieve better (worst-case) safety margins at reduced (total) power consumption. Because the machinery no longer needs to be designed around two "dumb" thermo switches and do a little extra in case layers of varying temperature manifest after two or more spaced periods of consumption. With continuous monitoring in software, you can integrate the worst-case bacterial growth based on time elapsed outside the "practically safe" temperature ranges. Then the tank always knows what is needed, and can both operate on tighter margins and reliably know when reducing or delaying power draw is ok.

Some settings are flat out refused (for "security reasons"). And with each new update there are a few new popups / invitations to try this new feature / re-enabling the v2 of the thing of which the v1 was already opted out in the policy. And it seems like you cannot apply new policy while the browser is running - meaning it cannot be used to roll out hotfixes without interrupting the work of currently unaffected workstations.

And then there is the syncing. If you want to manage & sync history, bookmarks and the password managers content.. you are probably going to find that easier by overriding the builtin features with 3rd-party extensions, as the builtin sync feature is very much tailored to the needs of privately owned devices and one-device-at-a-time usage patterns.

This one sounds new to me.

For a more proper solution, you could try to convince Mozilla that granting every website uncapped multi-threading and direct GPU access is a bit much. If webgl/webgpu truly is a must, then maybe each website permission should start with a single-threaded software-renderer that behaves indistinguishable on all supported platforms. And only after granting the website that extra permissions let it determine that a more powerful GPU is available.

Now that you can stuff an entire room with only high-G-resistant solid state drives, there should be fewer excuses for losing machines before determining a fire suppression system to be either inoperable or insufficient (but never tested and measured under realistic conditions).

I imagine there has, for a very long time, not been a need to specifically write down what that field-specific vision is and how exactly history teaches us that there really only is one scientific method. Some future LLM will surely be able to explain this in their place, so mathematicians can stick to their primary fields instead of having to become experts in teaching the theory of teaching.

The problem to be solved was not to spew out maximum lines of text containing some greek letters per hour.

It was to write down iterative progress in conceptualizing, modelling and consistently explaining difficult questions - in a way that advances human understanding. If nobody bothers to read through 50 pages of gibberish that may or may not be containing some insight, then the total problem solving remains zero.

But is is useful in related cases. I have now had two separate incidents where this would have saved me the hassle. Both were service providers which unilaterally tried to deviate from contract terms. One was possibly a unintended billing software upgrade where they suddenly added an extra item to a 10 year contract that did not belong there, the other was an apparently profitable "lets just try and see what percentage of customers notice" dick move. I should not have needed to care about this, both companies should have just been slapped with a hefty fee for requiring their and my bank to take a look, and then figure it out on their own instead of me having to call once to fix the problem for the future, and then call again to remind them about reimbursing the delta from past billing intervals.

What would be preventing a forge from answering with a reference to schroedingers octocat when inquired about the yet-undefined properties of a newly created repository? The first pushing client explicitly looks for it, and no final decision has be made server-side until someone wants to take a peek, no?