The copy on the linked "UK geoblocking" page doesn't contradict that, though.
The authors say, basically, that there's a risk of prosecution in the UK that would financially devastate anyone that works on the project, and that the act of determining how to comply with UK laws is itself an extremely resource-intensive legal task that they can't or won't do. In other words, they're geoblocking the UK not out of activism but out of pragmatic self-preservation.
That's not in any way mutually exclusive with collective action.
...also, couldn't deciding to geoblock the UK be a form of collective action? If that's what you originally meant, I sincerely apologize for reading it backwards.
To me it just seems like they are prejudiced against Brits or something.
I don't buy their statement about legal concerns given it's as vague as GDPR, and equally as inapplicable to a www git, and yet they've not banned the EU.
It's quite toxic to ban a whole country from your project without good reason. I've seen people break more of a sweat worrying about whether Russia should be banned from open source projects than the UK. It's not unfortunately unexpected, people love being ignorant about the UK.
Starships are a boring transport layer, implementation detail.
Being a part of a Q continuum, a disembodied consciousness that can appear wherever whenever, while still retaining a memory/sense of "self" is a far more interesting a dream.
Starships titillate people who tinker with machines. Not very optimistic if we are dragging along service jobs to explore the cosmos.
All programming achieves the same outcome; requests the OS/machine set aside some memory to hold salient values and mutate those values in-line with mathematical recipe.
Functions like:
updatesUsername(string) returns result
...can be turned into generic functional euphemism
takeStringRtnBool(string) returns bool
...same thing. context can be established by the data passed in, external system interactions (updates user values, inventory of widgets)
as workers SWEs are just obfuscating how repetitive their effort is to people who don't know better
Have you worked in software long? I've been in eng for almost 30 years, started in EE. Can confidently say you can't trust the humans either. SWEs have been wrong over and over. No reason to listen now.
Just a few years ago code gen LLMs were impossible to SWEs. In the 00s SWEs were certain no business would trust their data to the cloud.
OS and browsers are bloated messes, insecure to the core. Web apps are similarly just giant string mangling disasters.
SWEs have memorized endless amount of nonsense about their role to keep their jobs. You all have tons to say about software but little idea what's salient and just memorized nonsense parroted on the job all the time.
Most SWEs are engaged in labor role-play, there to earn nation state scrip for food/shelter.
I look forward to the end of the most inane era of human "engineering" ever.
Everything software can be whittled down to geometry generation and presentation, even text. End users can label outputs mechanical turk style and apply whatever syntax they want, while the machine itself handles arithemtic and Boolean logic against memory, and syncs output to the display.
All the linguist gibberish in the typical software stack will be compressed[1] away, all the SWE middlemen unemployed.
Rotary phone assembly workers have a support group for you all.
But that would require terminally online frogs acting in their collective interests, not isolating at home hoping the heat never reaches them.