Just a few minutes ago the german government announced that the village #Lützerath will be excavated to get the coal below. The whole village is squatted by climate activists, there are tree houses and more.
If you can, help to defend the village against fossil capitalism #LütziBleibt
mh+, medication
As I've been taking Ritalin (generics) for a while now, I've noticed my preference changing a bit - I now like to slightly "underdose" it, and then spike it up a bit with an occasional cup of tea.
This gives me a bit more of an 'ebb and flow' in my mental state, where I don't *constantly* feel one way or the other, but it can fluctuate a bit between 'relaxed focus' and 'slightly chaotic excitement'.
Really seems to help in continuing to feel like myself with eg. excitement for my own projects, while also giving some much-needed rest from a constantly-chaotic brain... while still mostly preventing brain fog!
video game startup sequences are really weird
and I'm not talking about the short videos that get played when you open a game
Guild Wars 2 starts up with a maximized white rectangle that has a title of "U"
it briefly changes to "Untitled" before the game starts accepting input
I would wager that the number of people in the world who know exactly why it does that is less than five
And that makes it all the more irritating when you're one of the few people who *has* actually looked into it, because you end up spending all your time and energy arguing with what essentially boils down to religious beliefs strongly held
Like, the vast vast majority of developers is basically just going off vibes and whatever assumptions/beliefs are considered the social default for their particular programming community, almost nobody has actually looked at what's going on or why
#NixOS people are serious about testing
Their testing automation is impressive!
Firefix is tested by opening a page (from valgrind man page), playing some sound, verifying some sound is played, closing a tab, display the developer tools. If anything fail, then the test fails
https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/firefox.nix
Openarena (Quake 3 open source reimplementation) is tested by running a server, connecting two players, verifying the clients connect to the server
https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/openarena.nix
Minecraft client is tested by running the client in a VM and use OCR to detect if it asks for creating an account
https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/minecraft.nix
software development, politics adjacent, long
(Another way to look at this, is that "just write efficient code" is an attempt to solve a collective problem with an individualist solution, and I hopefully don't need to explain why that is doomed to fail)
software development, politics adjacent, long
Potentially controversial opinion: I think that "making software more efficient" is the wrong thing to focus on right now.
There's a significant kernel of truth to the idea that "it's easy to make good code performant, but it's hard to make performant code good" - and so before going all-in on optimizing code as the primary objective, we should make sure that we're optimizing the right thing.
And right now, we're not. We're very much not.
There are significant problems to be solved in how we address software development, and the power dynamics embedded into it - the most obvious example would be the still-widespread fear of dependencies, which actively interferes with making software work better for people, and results in an endless treadmill of broken shit.
And guess what, there *are* significant efficiency benefits to be gained here - everybody using the same well-optimized implementation is going to be much better than everybody using their own homegrown half-optimized "clever" implementation.
But by putting all the focus on software efficiency and performance as the #1 priority, we risk removing all the oxygen in the room for figuring out better ways to deal with dependencies and many of the other industry-wide problems I haven't even mentioned here yet, and ending up in a *worse* place (even efficiency-wise!) than where we *could* be if we started with other problems first.
TL;DR: software efficiency and performance is important, but if you treat it as a goal to chase directly, you will end up with broken and faux-simple software that isn't even as efficient as it could be. Fix the big problems with software first, *then* think about how to optimize the remainder.
(And it will probably come as a surprise to nobody on here that an anarchist view of the matter presents a concrete solution to every single one of these problems)
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
Feel free to flirt, but if you want to actually meet up and/or do something with me, lewd or otherwise, please tell me explicitly or I won't realize :) I'm generally very open to that sort of thing!
Further boundaries: boosts are OK (including for lewd posts), DMs are open. But the devil doesn't need an advocate; I'm not interested in combative arguing in my mentions. I am however happy to explain things in-depth when asked non-combatively.
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.