

There are edible talers: https://de.wikipedia.org/wiki/Schoggitaler 🙃
There are edible talers: https://de.wikipedia.org/wiki/Schoggitaler 🙃
I guess, kinda? In my head, a Verein is definitely more of a hobby/socialising thing, but I do have to say that “club” certainly doesn’t feel impactful enough. Like, Germany as a whole would fall apart, if you took the Vereine away.
For example, the Red Cross is an e.V. here. There’s e.V.s that support the local voluntary firefighters (although those are also organized by the municipality). We’ve got big-ass nature preservation e.V.s that do really important work in suing awful corporations. Local sports organizations and orchestras and whatnot are also organized as e.V.s. And perhaps the most relevant in this community is the KDE e.V., which helps organize/assist the wider KDE community.
So, yeah, some of them definitely do work that one might expect from a charity…
You have to think of them more like a club rather than a non-profit company. Their legal form “eingetragener Verein” does mean “registered club”.
Basically, here in Germany, you can register a non-profit club and then you get exempt from taxes. And folks who donate to your club can also get that donation exempt from their taxes.
I have a web music player that I’ve developed, and while it was never really intended to be used by others, I thought I had generally followed accessibility best practices. After using it for about two years, I realized that I never even implemented keyboard shortcuts. 🫠
Which is to say, one shouldn’t assume devs to know what they’re doing. At some point, I’m also just a user and I use software like everyone else does, meaning I pick out a path that works for me and then I hardly look left and right from there.
Features not being tested when you don’t use them yourself, that happens with any feature. But it’s much worse for UI features, because those are difficult to automate tests for. And accessibility is in an even worse spot, because it necessarily opens up a separate path, which is going to be invisible to me as a user, so it gets covered by neither automated tests nor by me just using the software.
I have to go out of my way to test accessibility, which means I have to be aware that a change I’m making might introduce a regression. That’s genuinely how lots of amateur developers work, which is probably the best explanation why accessibility support is often so amateur-ish…
I don’t think that was entirely serious…
I also have basically only my personal experience to go off of (from studying computer science), but I never had to plug hardware into my laptop. Printers were available over the network and the one time we worked with hardware, they had dedicated lab PCs there, which had the necessary software pre-installed.
From what I’ve heard on the internet, that’s quite a common theme. Lots of hardware equipment is ridiculously expensive, so you don’t go buying new equipment when accompanying software doesn’t work on newer operating systems anymore. Instead, you keep a PC around with that old OS and the software, specifically for operating that hardware.