• 17 Posts
  • 1.41K Comments
Joined 5 years ago
cake
Cake day: May 31st, 2020

help-circle


  • 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…





  • Ah, damn. There’s folks out there who either like C or dislike Rust for whatever reason and they’ll always try to caveat what you say about this topic, so I made sure to only list facts. That’s why I got kind of angry when I thought you were still trying to caveat it, without spitting out whichever fact you thought was wrong. 🫠

    Any particular part you didn’t understand or just too much tech mumbo jumbo in general?





  • 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 mean, there’s definitely gonna be worse out there, but I once saw a tattoo on an online post, of presumably their date of birth in roman numerals.
    Problem is, there was only one “M”, so it looked something like: IV/X/MCXCIV

    But I figured, alright, let’s not assume things, maybe they’re a history buff and something cool happened on that day in 1194.
    But if I remember correctly, I found some list of all Wikipedia articles for specific dates and that day did not have an article, because nothing noteworthy had happened.

    So, yeah, I guess we do have to assume that they are in fact a vampire.




  • I think the main reason why Word is losing mindshare, is because it was designed for paper. The whole formatting system makes the assumption that there’s a fixed width and height into which your text and images fit. In reality, a phone screen is a lot narrower and a widescreen monitor a lot wider.

    Markdown never made these assumptions. For the most part simply because plain text reflows to fill whatever space you give it. But there’s no way to position an image either, I imagine mostly for simplicity’s sake. It can look goofy at times, but it never looks broken.
    That’s why I can write this comment on my phone and someone else can look at it on desktop and it’s perfectly readable in both scenarios.