pupbiru

blockchain as a core technology isn’t user-friendly… it should be hidden, and you’ll never know when it’s doing interesting things. it was never going to revolutionise the world, but that doesn’t invalidate its usefulness in niche situations

… it shouldn’t be used for 95% of the garbage people have built with it - and for NFTs that’s more like 99%

absolutely this

youse and torlet

I’m from Australia and I’ve started calling all groups of people yall because it’s gender neutral… very unaustralian term, and I love so much the irony of iconic southern terms being used to support trans activism

And any partner of mine in that situation would be like cool… 3some? And everyone has fun

the way people use NFTs with art are certainly absurd, but even the core technology of NFTs is actually excellent

a gift, or a test?

i will never understand the inability for people not to have amazing sex with their friends

the various github-supplied actions are good example:

https://github.com/actions/setup-python

the action.yml here is the metadata for an action (and you invoke this action by simply referencing actions/setup-python - perhaps with a sha or tag or something to pin it - and the runner clones and runs it, making custom actions simply code with no build process etc necessary which is very nice to not have to bootstrap your build process with a build process eg docker build)

see the “runs” section there - it invokes node20 to run the action, and specifies some code to run to cleanup

in the src here we can see what i was mentioning as well about having bi-directional comms with the CI system

https://github.com/actions/setup-python/blob/main/src/setup-python.ts

line 54 & 55 we have core.getInput and core.getMultiLineInput, 59 we have core.warning (so logs are formatted and filterable etc - these messages also show up in the build summary; similarly line 100 we have core.startGroup), 154 is core.setFailed so you get proper failure reasons rather than “the last line of stderr”

now, none of this is specific to running in a real language - in fact i believe all this information is communicated over stdout or stderr - but the ease of simply creating a repo with code in it, and having that as a reusable CI step without worrying about docker container hosting, and having that able to have semantic meaning for its inputs and outputs (and proper reliable escaping of the special CI communication prefixes) is something that kinda doesn’t exist outside of this style system

Hmmm I mean I guess we’re a very big country for our population so maybe the mining and interstate rail overwhelm the metro and Sydney-Melbourne networks… I’m just surprised it’s by more than 80%

personally i have a very big preference for the “actions” model: actions are “real” code; not bash - so there’s actual variable passing and communication with the CI tool (eg an action can tell the CI system to set a secret value, and the CI tool then hides that value from console output in the future). you can do these things with bash as well, but bash isn’t really a great language - i’d trust node far more to, for example, generate a hash or a JWT etc and actions then have access to the entire of NPM for libraries

these kinds of things (not only this) make it far superior to a bash-based system IMO

soooo does the difference between x-handed and x-handed 20% multi-track mean that the x-handed colouring has >80% single lane tracks?

i live in australia (left-handed), and… that seems… implausible

the rust devs wanted to CREATE official structure definitions that don’t exist in C so that there was more semantic meaning to the APIs