The difficulty would indeed adjust to factor the new hash - and if you were someone still trying to use more energy on older, less efficient, miners, you'll be left in the dust comparatively, even if you're still consuming more energy than others using the more efficient miners.
Energy and hashrate are definitely NOT unconnected, it's just that they're not connected at a fixed 1:1 ratio. The efficiency of the hashrate production is the abstraction between Bitcoin and the energy used to mine.
The mistake I meant was not including the city
Which is fine for posters that go up around town, notsomuch for posting online
At least he asked for a book and not an iPad
Biden calls Hamas attack worse than 9/11
From RT
October 7 was “like fifteen” Al-Qaeda attacks, the US president said in Tel Aviv US President Joe Biden on Wednesday argued that the Hamas attack on Israel was worse than the 2001 terrorist attacks on New York and Washington, and vowed that America would “forever” stand with the Jewish state. At least 31 Americans were […]
Oct 18th 2023 1:51pm EDT
Source Link: https://www.rt.com/news/585281-biden-hamas-911-israel/?utm_source=rss&utm_medium=rss&utm_campaign=RSS
Internet Archive Link: https://web.archive.org/web/20231018175627/https://www.rt.com/news/585281-biden-hamas-911-israel/
Share, promote & comment with Nostr: https://dissentwatch.com/boost/?boost_post_id=643177
Hand him a shampoo bottle that's what we all used to use before smartphones 🤣
Good thing I know the Avenue
But not the city
FYI the forward slash interrupts and breaks the hashtag on Damus. Not sure how other clients behave.
The same on Amethyst
I'm old enough that when I was taught, flowcharts and pseudocode were considered equally sufficient documentation of what the code was supposed to be doing, and simple enough to be easily understood.
But I'm literally a dinosaur in this field (pre-Y2K) so what do I know
I do diagram my code, but I agree it's pointless to go back and keep the chart in sync with the code once you've written it. The better way is to enshrine the intent of the diagram in automated tests.
I personally follow the method in Reliable Software to plan out my code. It keeps your code neat and clean from the very beginning.
https://archive.org/details/myers-reliable-software-through-composite-design/page/n1/mode/1up
If your documentation falls out of sync with the production code you're introducing an unnecessary nightmare for whoever may need to update or maintain the code in the future (which may end up being YOU)
KYC to leave your home coming soon
Flowcharts and/or pseudocode are a low time preference investment of time and effort. In the beginning they merely consume, but over time they pay dividends in efficiency.
The point is that hashrate is what's desirable (and directly linked to Bitcoin), not energy use.
If someone improves efficiency such that energy use is decreased while hashrate increases, THAT is desirable.
Of course, in the real world every time efficiency increases, energy usage goes UP, not down, because the efficient use of energy makes it more affordable and thus available to a wider market of users.
But the energy consumption is incidental to the generation of hash, or else we'd all just be firing up the least efficient (but cheapest) miners available in order to consume as much energy as possible, which is obviously not the case.
