People say this place is a street.
But they behave like it's their living room.
While in reality, it's a soapbox on the main square.
Meanwhile all I wanted is a watercooler.
1. Reinvent a square wheel
2. Understand what's so hard about making wheels
3. Observe how a round wheel someone invented a while ago performs better than your square one.
4. Appreciate the brilliant and simple solutions to all wheel design issues that a round wheel implements.
5. Throw away your square wheel.
1. Reinvent a square wheel
2. Push it to production
The real world Matrix is the Spectacle woven by competing ideologies. Taking the "red pill" means giving up on certainty, because all totalitarianism requires mass belief in eternalist certainty, and true freedom requires an ability to live with moral courage in the face of uncertainty.
#ShowerThoughts "All isms are wasms". Eternalist ideologies attempt to deny the 'patterned but nebulous' nature of truth, by clinging to an Eternal Truth even to the point of self-delusion ("Jesus is Lord!", "All is one!", "It's all the Jews!", even "It's all the capitalist elite!").
Oh, and did I mention pids are race-y?
There should be a purely capability-based way to do it, right? (and by capabilites I don't mean POSIX capabilities, I mean FDs. I mean i-can-name-it-so-i'm-allowed things).
But let's make it more lax:
Can you figure out a way to do this without looking up PIDs of third processes (i.e. other than your own and your children's) ?
I mean, you could probably use SO_PEERCRED to find the PID of the client, look up all its ancestors in procfs, check if you have any of them in your PID->client hashmap, if so, check if all their surfaces are on the same workspace, and if so, put the new client's surface on that workspace, too.
But this is a hack.
SO_PEERCRED has many issues compared do SO_PASSCRED, and assuming procfs is mounted and you have permissions to walk it is awful as well.
So I have a terminal in one sway workspace, and in it I run
pdflatex foo.tex && mupdf foo.pdf
it takes a minute or two to build, so I switch workspaces and do something else in the meantime.
And then a mupdf pops up out of the blue on my current workspace.
Question: why can't we make new processes' windows spawn on the same workspace as their parents?
INPUT article on MNT Reform: “Perfect for the coming apocalypse”! https://www.inputmag.com/tech/this-is-the-laptop-youll-need-when-the-meteor-hits
Blazing hot tech take // protocols
Text protocols are good, actually!
It's REALLY, REALLY COOL being able to just, send text at a socket and have it do stuff for you.
And sure it's /technically/ inefficient, but given that they were using text protocols back when they were /way/ more resource-constrained than we are now...
Looks like microsoft is trying to make a whole alternative GUI stack on Linux that only works when running as a VM under Hyper-V...
> If you want to know how to accelerate that process, go debug the code of others
CompSci student at Uni of Warsaw
Linux geek, trying to be a sysadmin
Likes The Unix Way
🇬🇧🇵🇱(🇯🇵 a bit)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!