JKB @jkb@octodon.social

More perspective?

The global energy consumption in 2017 was 22.3 terawatt hours.

If we moved all financial transactions over to Bitcoin, we'd require over 1000 terawatt hours... each day(!) for Bitcoin transactions alone(!).

That doesn't even factor in that Bitcoin's energy consumption will be exponential to the amount of transactions.

'Colonialism had never really ended': my life in the shadow of Cecil Rhodes http://www.theguardian.com/news/2021/jan/14/rhodes-must-fall-oxford-colonialism-zimbabwe-simukai-chigudu

People who tell computers how to behave, what would you rather be called?

(I can only put 4 choices, write-ins encouraged in replies, "hacker" is another term I would have liked to include.)

Oh shit, @pla got hit by a car..
He was one of the first person I've ever followed on the fedi. His unique mixture of of tech and bicyles will be missed 😭

https://bbs.kawa-kun.com/notice/A33q0nw26SNFq5BYyu

He died doing what he loved.
Fuck cars.

Recently I learned that the Spread syntax in JavaScript (...) allows the inner expression to return something falsy, and that just won't insert anything in the object. That allows you to turn this: {...(maybeObject || {})}‌ into this: {...maybeObject}. Neat!

Actually even something like {...23}‌ turns into an empty object, it's not just falsy things that get filtered. I guess is all non-Object things. Not even a simple Map gets inserted. Arrays are perfectly fine Objects with indexes as keys though. =)

TIL that this neat property only holds for the object Spread syntax. The array Spread syntax strictly requires an iterable. So you *do* need to have [...(maybeIterable || []). If you try [...false]‌ you get TypeError: boolean false is not iterable (cannot read property Symbol(Symbol.iterator)). That's disappointing, the new syntax additions otherwise have tended to be more consistent than that.