Autonomous Trap 001 by James Bridle comes to mind
238 karma · joined April 13, 2009
>import {URLSearchParams} from "url"; >const {URLSearchParams} = require("url");
or different destructuring from regular javascript
>import {URLSearchParams as P} from 'url'; >const {P: URLSearchParams} = require("url");
also you could have used await with require, it would be intuitive for developers as they likely have come across the same syntax before.
> const lib = await require("lib")
I don't see any argument why the require approach couldn't have been implemented in the browser. What is the actual gain from using ESModules syntax?
Entertainment? Random Number generator? Maybe they are in the future and doing some historical analysis. Plenty of reasons to spend resources.
They might need combine/reduce the elements. Or use a canvas?
Starbase streetview is pretty cool
https://www.flickr.com/photos/whoisstan/52146306564/in/datep...
It seems to inspired or in the spirit of ‘The Ministry for the Future’ by Kim Stanley Robinson.
“ It’s called Carbon Coin in the book, a Bitcoin-like currency that the Ministry gives out for carbon sequestration — that is, any project that sucks CO2 out of the air, whether it’s carbon capture or farmers rewilding their fields — at a rate of one coin to one ton. Oil companies get coins if they stop being oil companies, basically, leaving their assets in the ground for a century or so. Coins can then be bought and sold on currency exchanges like any other.”
The only argument I can see is that the sheer resource hunger will force our hand in using renewable energy. Of course, I am not saying this is a good argument at all.
There is no such thing as virtual energy. And the other forms of payment we use are a million times more energy effective.
What bothers me is that newsletters as this one who I believe are widely read serve this up as a good idea.
https://www.exponentialview.co/p/ev-315
%)