I see your concern, but in practice that’s not what happens in languages like Java and Python with exceptions. Not checking for exceptions is a choice because everyone knows you need to check in your top-level functions. Forgetting to catch is a problem that only hits newbies.
Oof, some of these comments. Sorry on behalf of the edge lords, OP.
But the entire point of Rust and Result is… to force you to make a choice of what should happen
Checked exceptions also force you to handle it and take way less boilerplate.
Zigbee or really any Bluetooth alternative.
Bluetooth is a poorly engineered protocol. It jumps around the spectrum while transmitting, which makes it difficult and power intensive for bluetooth receivers to track.
Feel free to add it to the list. It’s Wikipedia.
Cool, you should add those in and find some sources. It’s Wikipedia
Because security through obscurity is not security at all.
I’ve been a big fan of monorepos because it leads to more consistent style and coding across the whole company. It makes the code more transparent so you can see what’s going on with the rest of the company, too, which helps reduce code islands and duplicated work. It enables me to build everything from source, which helps catch bugs that would only show up in prod due to version drift. It also means that I can do massive refactorings across the company without breaking anything.
That said, tooling is slowly improving for decentralized repos, so some of these may be doable on git now/soon.
The author neglected to link to the actual report. Page 34 and 35. The Scope 2 stats the article cited don’t account for clean power generated.
Their link for the claim “Google cited AI as the cause” doesn’t mention power at all.
The link for the Microsoft numbers takes me to a report saying the 30% number is for Scope 3 emissions, which have nothing to do data center power usage.
They just added a fee so that AWS can’t copy it without paying. What’s the big deal.
Too long, didn’t read