• 302 Posts
  • 2.81K Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle












  • Well, I did it this year finally after thinking about it for a decade+.

    One of the reasons I did it was to document stuff for future me - if I never need to redo anything I wrote about, I have a perfect manual.

    The other reason is to help the community. I sometimes tend to write about fairly obscure things (like creating a Matrix bot with E2EE enabled, or mixing Go and PHP using FFI) that might actually help someone if they search for it.

    I don’t know about you, but whenever I ask an AI something that’s not really mainstream knowledge, it sucks so much so I have to search anyway, so tech blogs will always be needed.

    Edit: I also took it as an opportunity to learn about ActivityPub, my blog is fully federated and you can read it here on Lemmy if you want. So if you can find some learning opportunity in there, go for it!


  • The textbook definition is being aggressive without partaking in direct aggression. A simple rule of thumb difference is that with passive aggressive behaviour you can pretend you didn’t know you were aggressive.

    Like, if you throw a brick at your neighbour’s window while he’s watching TV - there’s no way you can twist it as meaning anything else. That’s the normal non-passive aggressive and you can’t really pretend you didn’t mean it the way you did it.

    If you pour water in the middle of harsh winter in front of their door, that’s passive aggressive - you avoid direct confrontation (unless they happen to see you) but are aggressive towards them. He might suspect it’s you (you threw a brick through his window after all!) but he can’t prove it.


    That’s what’s frustrating about passive aggression - everyone in the room (including the passive aggressive person, their target and any bystander) knows what’s going on, but it’s not direct so the aggressor can claim “omg I didn’t mean it that way.”







  • It’s gonna be different case by case, but my best guess would be it starts as wanting to please the community, then realising Linux users get weird errors they never hear about from Windows users and then deciding that all 5 Linux users are not worth it if the issue doesn’t concern majority (Windows) users.

    As for missing features, usually it happens because they use some Windows-native feature (like direct DirectX calls) which saves them implementing workarounds for their engine. And porting to some Linux api is delayed indefinitely for the same reasons as bug fixes: not large enough user base.


    Linux gamers often say stuff like “it’s literally one toggle in [insert game engine here]” but that’s never the case. Doesn’t mean new devs don’t fall for it.

    IMO we should fuck native Linux builds - game engines are complex and messy beasts, building on one platform and testing on Proton is the best for everyone, IMO.