I thought google did this versioning thing for libraries before, but it was stopped for reasonable reasons (g3 components).
Basically if you could pin lib versions everyone would be stuck on old versions for a long time, causing difficult debugging work for each user of the library. You'd then also have all sorts of diamond problems: what if you want newest absl but older bigtable client?
It's a difficult problem no matter which way you go.
I can believe this. Around the time I left people were patting backs for fighting racism by getting rid of terms blacklist/whitelist.
Not something I feel super strongly about, but the fact that it's so scary to go against these stupid ideas is annoying. It's pure politics, there's nobody benefiting from this except the people claiming impact for antiracist work in their perf.
There's very little you need exceptions for with STL. Data structures, algorithms, etc. all work just fine without exceptions.
C++ without exceptions is great. Google doesn't use exceptions and they still use STL. Gamedevs usually don't use exceptions and they're fine. Just use some other mechanism for errors, like error codes, absl::Status, std::expected, etc.
Google did not do exceptions due to legacy code base reason, in its announcement it says for new code it will do exception, it just had too many old code and can't do exceptions.
Most STL operations and iteration etc will throw exception for errors, if you disable exception, any of those errors, be it recoverable or not, will just std::terminate, which might not be ideal.
I interviewed at Google once and during some whiteboard forgot to check malloc for NULL return, then mentioned, "oh yeah at <former company> malloc never returns NULL" and the interviewer commented "at Google, malloc spawns a new data center."
You can buy drugs and other illegal things off the internet (tor), that's very useful for some people. Basically crypto allows for transactions that could otherwise be blocked or easily tracked by central parties (1). It can also be used to bypass gambling laws.
For legal purchases and activities crypto is useless, regular money is much more practical.
[1] depending on which crypto and how it's used tracking is possible, so care is required (especially) when converting dollars to crypto.
> You can buy drugs and other illegal things off the internet (tor)
Can you? After that huge bust a few years back, I figured that particular usage was marginal at this point. Seems like the only use for crypto is ransomware, dodging taxes or smuggling embezzled money out of your country.
Yeah, there are still plenty of drugs on the darkweb. Busting a few dealers doesn't eliminate demand, and in-person dealers don't have a "reviews" page for their products and behavior.
There doesn't even have to be a conspiracy for this to occur.
Companies always want to seem like the good guys, so they'll jump on any trend that doesn't hurt them. BLM, LGBTQ+ (), etc. are issues that companies don't have to lose anything to take part in. Advocating for (e.g.) unions is something the Amazons of the world don't want to promote. This creates bias on every level which suppresses topics that are inconvenient for the powers-at-be.
People fighting over race is very convenient for the 0.01%, so no effort will be made to end that fight.
( Not that these aren't important, just that there are important issues that are not discussed on the same level.)
This is wrong, the number of transactions has (almost) nothing to do with the energy usage. I wrote almost in brackets because the transaction fees contribute slightly to the total compensation of the miners. So it is mostly the block reward that determines the energy usage (for now)
I can veryfy all Bitcoin transactions ever happened on the network on my laptop in a few days, I'm sure it's less than that, my Apple M1 laptop is quite energy efficient.
New blocks are created with transactions in them and can’t be verified if they haven’t been mined, because verification works by checking the hash that the miner found.
Transactions that are not yet part of a mined block cannot be verified.
What you wrote is all correct. Just don’t confuse creating the transaction and adding to the network (which is relatively expensive) with verifying (which is cheap, an SHA-256 hash can be computed in 2 days by a human with pen and paper, and for verifying the transaction you need an exponentiation on an elliptic curve, which is still efficient, though slower).
There's a lot of convenient new instructions in avx512 that can work on 128/256-bit vectors. I'm guessing that those wouldn't throttle more than regular avx.
Basically if you could pin lib versions everyone would be stuck on old versions for a long time, causing difficult debugging work for each user of the library. You'd then also have all sorts of diamond problems: what if you want newest absl but older bigtable client?
It's a difficult problem no matter which way you go.