Electricity prices are set by the marginal producer, which in the UK a lot of the time means gas turbines which are expensive to run. Which mainly means that the renewables plants are making money hand over fist, creating a big push to create more. It's only once that percentage grows enough that the price pressure will go downwards in general. (currently the UK is roughly an even split between gas turbines, nuclear/biomass, and renewables). You can already take advantage of the low price of renewables in some cases, though, if you have a flexible tariff and electricity demand (like a water heater, a house battery, or charging an EV), by drawing when the gas turbines are not necessary to meet demand.
The interesting part is that 130 Billion of the savings were in reduced gas prices as it reduced demand, particularly in winter, and freed up gas storage.
And this is depsite an effective ban on constructing onshore wind in England from June 2015, more than half the 2010 to 2023 time period studied.
A few weeks before the tariff idiocy, I paid $320 including shipping for an ebike battery from the EU. When it arrived, it included a bill for an additional $350 from US Customs. That's insane, I refused.
When returning to sender, the package disappeared, presumably into Customs. I'm out $320 and still no battery.
One additional bit of context, they provided guidelines and instructions specifically to send emails and verify their successful delivery so that the "random act of kindness" could be properly reported and measured at the end of this experiment.
The comment was perfectly valid and topical and applicable. It doesn't matter what kind of improvement Meta supplied that everyone else took up. It could have been better cache invalidation or better usb mouse support.
I should probably ask what experience do you have writing hardware drivers for the Linux kernel, but it's pretty obvious the answer is: none. I actually burst out laughing reading your comment, it's ridiculous.
My anecdotal experience interviewing big tech engineers that used Rust reflects GP's hunch about this astonishing experience gap. Just this year, 4/4 candidates I interviewed couldn't give me the correct answer for what two bytes in base 2 represented in base 10. Not a single candidate asked me about the endianness of the system.
Now that Rust in the kernel doesn't have an "experimental" escape hatch, these motte-and-bailey arguments aren't going to work. Ultimately, I think this is a good thing for Rust in the kernel. Once all of the idiots and buffoons have been sufficiently derided and ousted from public discourse (deservedly so), we can finally begin having serious and productive technical discussions about how to make C and Rust interoperate in the kernel.
Nowhere did he argue that. What he actually argued--poorly and offensively--is that it's "pretty obvious" that bronson has no experience writing Linux hardware drivers.
