• 0 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle














  • WSL works fine. The only issue I’ve ever had with it pertains to mouse weirdness with SDL, and I had the same exact issue in a level 2 VM due to the way they handle mouse input. I still use it all the time when I’m not working in Linux for one reason or another.

    More importantly, that’s not the point: bringing up WSL already means we’re talking about at most 1% of Windows users. You’re failing to consider the user experiences of

    1. the person who can’t tell you the difference between an OS and a web browser (usually also the person that thinks pressing the power button on the monitor turns off the PC)
    2. the prolific email answerer, who generally refuse to use anything other than Gmail (see person 1) or Outlook (bonus points if they still have an Exchange server with a custom “lastlame.com” domain they set up before the dot-com bubble burst)
    3. the godmother of lost kitten posters and printed-out recipes (LibreOffice doesn’t have Comic Sans or WordArt, and my beige-plastic printer from 2001 is difficult enough to use on Windows!)
    4. the Gamer™, who would be pissed to find out they can’t install Razer spyware to make their $500 in peripherals induce seizures to the beat of skibidi toilet
    5. the Nvidia user, who wouldn’t have that bad of an experience these days, but has heard enough horror stories to not even consider it
    6. the artist (unless the state of drawing tablet support has changed recently; I haven’t checked)
    7. the hi-fi boyz (this post was brought to you by HDR gang)

    THESE people represent a strong majority of PC users, and they all have reason (good or bad) to avoid Linux. The fact of the matter is, if you’re a programmer like me or yourself, your opinion is skewed strongly towards Linux because the last 20 years of development were mostly fueled by the Android kernel and enterprise/datacenter deployments, both of which disproportionately benefit our use case.




  • Of course the Lemmy devs aren’t liable for GDPR violations; the admins are. That doesn’t eliminate the problem, though: if the Lemmy devs wish to see their software used as it is now in the long term, they need to introduce GDPR compliance tools. We should consider it gravely concerning that bad actors (e.g., a Reddit employee) can set up Lemmy admins for a massive GDPR suit at any moment.

    Edit:

    if the people complaining are so concerned, why do they not contribute the code to fix their perceived issues?

    I know it’s a stereotype around here, but not everybody on Lemmy is a programmer with free time.