They do shut off ("curtail") renewable energy because it is a problem - excess power can destabilise the grid, causing brownouts and blackouts and also physically damage grid equipment like transformers and transmission lines over time.
I agree - it's like a fun code-golf challenge in that you end up with awful, write-only code but you may well end up with a deeper understanding after solving it. It's for circumstances almost opposite to an interview.
The proposed solutions don't even work - for example the tan is only meant to display once per letter.
The actual question does at least ask when it's JS suitable and when isn't it - for example it's irritating to have to wait for a page to init just to be able to access a drop-down menu (hint: use active in CSS instead of a JS toggle).
It's definitely a problem with the grid, since too much supply is at least as big a problem as too much. Hopefully we'll get things like molten salt batteries so we can soak up this excess and decarbonise heavy industry.
Schedule, yes! We're very much in the minority on that one, but I'll keep on using it the right way, even if it doesn't seem to make sense when looking at other words like school.
I seem to use movie when describing the blockbuster/B-movie end of the scale, and film when talking about a quality bit of cinema. But I also am more likely to call a US flick a movie and a Brit one a film.
I like the sound of the word autumn, and particularly autumnal. I can see those reds and browns and feel the crisp air. Fall does give more opportunity for puns and easier rhymes, I guess.
I've gone the opposite way - I've been replacing my American pronunciations with the British ones, like leverage starts with lee, like in lever, and that (software) patent starts with pat not pait.
I think it's in response to my younger friends and colleagues sounding, to my ears, increasing American - they say gotten, zee, and on accident (things that are often more consistent, but just not cricket British). I'm old enough to remember the sound of dial up, so I probably wasn't as exposed to US media growing up.
And are bugs harder to find than carefully hidden backdoors? No-one noticed the code being added and if it hadn't have had a performance penalty then it probably wouldn't have been discovered for a very long time, if ever.
The flip side to open-source is that bad actors could have reviewed the code, discovered Heartbleed and been quietly exploiting it without anyone knowing. Government agencies and criminal groups are known to horde zero-days.
I wonder if the compiler checks to see if the calls are pure and are therefore safe to run in parallel. It seems like the kind of thing the Rust compiler should be able to do.
I like this idea of thinking about purchases in terms of per-use cost - this means you should spend more on mattresses and bed linen, underwear, office chairs and computer peripherals, etc.
I'm also a fan of working out how much a price-tag is in terms of how long you need to work to get the equivalent cash. Would I be willing to work for an extra two hours to get this thing?
Maybe millions of potential eyes, but all of them are looking at other things! Heartbleed existed for two years before being noticed, and OpenSSL must have enormously more scrutiny than small projects like xz.
I am very pro open source and this investigation would've been virtually impossible on Windows or Mac, but the many-eyes argument always struck me as more theoretical/optimistic than realistic.
Hmm, not really. It's only because it nerd-sniped someone who was trying to do something completely unrelated that this came to light. If that person has been less dedicated or less skilled we'd still probably be in the dark.
Deebster @ Deebster @programming.dev Posts 57Comments 963Joined 2 yr. ago
Interesting seeing how receiving money generated its own problems and work. They seem to be handling it well, though.