sorted by: new top controversial old
Love [Rule] in c/onehundredninetysix@lemmy.blahaj.zone
[–] 3 points 1 day ago

Really cool art but I have to fundamentally disagree. Hate of what is different is the most natural thing ever. It's better to acknowledge that we might all be a little bigoted sometimes than to pretend we are pure beings.

  • permalink
  • fedilink
  • source
    •
    fricken delicious in c/lemmyshitpost@lemmy.world
    ECB survey about new banknote design in c/europe@feddit.org
    Just got my 3rd tattoo! in c/tattoos@lemmy.ml
    Meme Got Upgraded in c/memes@lemmy.world
    Accurate in c/politicalmemes@lemmy.world
    [–] 43 points 1 week ago (9 children)

    Does anybody actually say that anymore? I think the whole "immigrants are taking our jobs" was an excuse back when racism wasn't mainstream. Now it is, so people don't use it anymore, they just say way more racist things instead. It's just a strawman at this point

  • permalink
  • fedilink
  • source
    •
    Autoritärer Staatsumbau in Reinform - Linksjugend in c/dielinke@feddit.org
    Am I the only one who thinks this? in c/memes@lemmy.world
    They always ask this and yet never want to hear the answer. in c/comicstrips@lemmy.world
    Ich🎵🎶📺iel in c/ich_iel@feddit.org
    Ich🎵🎶📺iel in c/ich_iel@feddit.org
    Ich🎵🎶📺iel in c/ich_iel@feddit.org
    10
    Why is it x.* but not x.& ? (discuss.tchncs.de)
     

    I'm currently learning the language, and I was wondering about this design quirk.

    Basically, if we have a variable x which is a pointer, we use x.* to get the value. This is much better than using * as a prefix, since the * might need to be applied to anything in the chain for complex access. I see the usecase.

    For example something like

    (*(*pointer_to_struct).struct_field_ptr).struct_field

    is much more clearly written as

    pointer_to_struct.*.struct_field_ptr.*.struct_field

    But then it feels really inconsistent that we don't do the same for taking a reference with &. Sure, we only ever take one reference of the entire value, so we don't have the same problem as above, but:

    We still have the issue that the & is not next to the value being dereferenced:

    &some_ptr.*.some_array_struct_field[5].target

    this takes the address of the target struct field, which is on the opposite side of the expression.

    It also just feels inconsistent.

    Additionally, I think the type declaration for a pointer should be &u8, not *u8. Since the & character is semantically equivalent to "address of", and * is more like "value at address".

    Thoughts?

    33
    What headsets are linux gamers using? (discuss.tchncs.de)
     

    cross-posted from: https://discuss.tchncs.de/post/55388559

    I made the mistake of believing some dumb guide online that recommended the Razer BlackShark v2 Pro for Linux. Literally the volume control is broken out of the box lol.

    I just want a wireless headset. For listening to audio. And a mic. Don't care for fancy features. Apparently too much to ask for a linux user.

    What are y'all using and how is it working for you?

    109
    What headsets are linux gamers using? (discuss.tchncs.de)
     

    I made the mistake of believing some dumb guide online that recommended the Razer BlackShark v2 Pro for Linux. Literally the volume control is broken out of the box lol.

    I just want a wireless headset. For listening to audio. And a mic. Don't care for fancy features. Apparently too much to ask for a linux user.

    What are y'all using and how is it working for you?

    154
    Windows-coded error (discuss.tchncs.de)
     

    Apparently, importing ~/.config/kglobalshortcutsrc is enough for the shortcut to show up in the System Settings, but not enough to load the shortcut. Disabling, applying and re-enabling and applying again also doesn't help, and neither does re-assigning to the same shortcut, which resulted in this lovely error dialog.

    view more: next ›