Our News Team @ 11 with host Snot Flickerman


Yes, I can hear you, Clem Fandango!

  • 1 Post
  • 321 Comments
Joined 2 years ago
cake
Cake day: October 24th, 2023

help-circle





  • So then what’s the fucking difference if they’re bitching about their issues with Windows versus bitching about their issues with Linux? Doesn’t that bring us back to the original post? Let people complain. If they’re going to have issues either way and bitch either way, why the fuck do you have to evangelize them to get them to shut up about the ones you’re ideologically opposed to? What are you really doing other than having them bitch about something you feel happy about? You haven’t materially made their life better, they still have computer issues they hate, but now they just have a smaller number of people they can turn to for help. Great job.



  • I hooked her up with a local computer repair guy that will do house calls and knows Linux because I live very far away.

    …is vastly different than what first post suggested, and literally ignored the major point of my original post which was that most people simply don’t have the time to figure it out and most also don’t have a Linux-repair-guy on hand. Talk about shifting goalposts here.

    Of course people have issues on Windows, that’s why they’re always bitching about it. You don’t think someone who likes to bitch wouldn’t bitch to their Linux-repair-guy when they had Linux issues?


  • Those who do their own troubleshooting will learn no problem.

    That stance I can agree with, but I fundamentally do not agree that Linux is appropriate for the kind of people who don’t do their own troubleshooting. Because my point is that is specialized knowledge that not everyone has the time to give to, which is why a lot of people don’t troubleshoot their own shit, because they have spent their skill points elsewhere.

    Trust me I have met lawyers and doctors who are fucking mystified by computers and don’t even want to get into learning the troubleshooting. That’s what they have IT departments for. Similarly, changing a tire might just be too much trouble for them and that’s why they pay other people to do it.



  • I literally use Linux in my daily life non-stop. My desktop is free from Windows and I run numerous servers for various services and microservices.

    I just fundamentally disagree with the hivemind that Linux desktop of any flavor is ready for casual user prime-time. Even if they don’t have technical issues with now that doesn’t mean they won’t have technical issues with it ever. In my personal experience, I have only ever had successful long-term rollouts of non-gui cli-only servers. I have always had issues of some sort crop up with desktop Linux eventually.

    Further, depending on the DE, getting things set up properly for someone who has, say, vision issues so everything is easily visible for them can often be a fucking nightmare of numerous different config files for different parts of the GUI. Linux accessibility options are notoriously bad.

    If you want to pretend Linux is a perfect solution for grandmas, go ahead, but as someone who is a Linux heavy user who doesn’t even use Windows anymore and hasn’t in a while I think that this attitude from Linux evangelists is deeply rooted in a rose tinted view of the OS and it’s user friendliness. And yes I use the term evangelist for a fucking reason, and that is because you people are as fucking pushy about your ideology as evangelical Christians.


  • They literally pointed out that a lot of the people saying this kind of stuff may genuinely be unskilled when it comes to computers in general.

    Why is it “trying nothing” when the other option to get up to speed enough to use Linux is to basically be taking some college-level courses on the side of their every day life just to be able to use their device appropriately?

    For people who aren’t tech savvy at all, “Ain’t nobody got the time for that!” is a completely fucking reasonable response to being told they need to go learn a bunch of shit about some subject they could give a rats ass about.

    It’s like telling someone who has a law degree and works 50 hours a week at a law firm that if they want more control over their car they need to take some courses on automotive repair so they don’t have to deal with an annoying repair shop. As above, ain’t nobody got the time for that!

    Literally every Linux nerd seems to forget that this is specialized knowledge that not everyone has dumped skill points into.





  • IPv4 has DHCP. Is there something in the way of applying a similar solution to IPv6?

    That in itself is implemented a few different ways, and each one is more useful dependent on your use-case, but these also have very little to do with how your ISP hands out the IP to your modem. When you get an IP handed out to your modem by your ISP, it’s often not being handed out by DHCP but an entirely different technology purpose built for whatever medium (cable/DSL/fiber) is actually going into your modem, so knowing their implementation is still important. Things work a little differently at enterprise-level. Although you’re not wrong that eventually there could be routers with auto-configuration based on which type of IPv6 network the router detects, there just currently aren’t any that I know of.

    But if you’re interested in the modern equivalents of DHCP you should look into SLAAC vs. DHCPv6 which are similar but oh so very different.




  • Snot Flickerman@lemmy.blahaj.zonetoProgrammer Humor@programming.devIt was
    link
    fedilink
    English
    arrow-up
    82
    arrow-down
    1
    ·
    edit-2
    13 days ago

    It’s like the opposite of Dr. House’s “It’s never Lupus.”

    “It’s always DNS.”


    I feel like we really need to speed up the embrace of IPv6 to solve this kind of issue. DNS is helpful to humans sure but a lot of these outages are triggered by services not being able to reach one another because they’re hard-coded to a DNS to avoid shifting IPs due to things like NAT.

    It feels like we could do an end-run around a lot of this by having a failover to an IPv6 address that is associated with the DNS entry if the DNS fails. Kind of like you generally have multiple DNS servers in sequence in case one of not-responsive, what if, at the service-level we stopped relying on DNS so much and instead used the benefits of IPv6 to not have services fail when DNS does? DNS should be for humans not for computers especially not in a world where IPv6 exists.

    (someone who is more familiar with the ins-and-outs of IPv6 is welcome to tell me if and why I am wrong in thinking this)