• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: April 3rd, 2024

help-circle





  • Jesus_666@lemmy.worldtoProgrammer Humor@lemmy.mlCommit
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 months ago

    I’m kinda planning on teaching my team how to use interactive rebases to clean the history before a merge request.

    The first thing they’ll learn is to make a temporary second branch so they can just toss their borked one if they screw up. I’m not going to deal with their git issues for them.


  • Jesus_666@lemmy.worldtoLinux@programming.devGTK Drops X11!
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Fair point. It remains to be seen how well this will work out for them. But given that doesn’t seem to be even a vague launch date I’d say there’s going to be plenty of time for a transitional phase where they can get their bugs sorted out – and the underlying operating systems can get Wayland running if they haven’t already.



  • If you use a .local domain, your device MUST ask the mDNS address (224.0.0.251 or FF02::FB) and MAY ask another DNS provider. Successful resolution without mDNS is not an intended feature but something that just happens to work sometimes. There’s a reason why the user interfaces of devices like Ubiquiti gateways warn against assigning a name ending in .local to any device.

    I personally have all of my locally-assigned names end with .lan, although I’m considering switching to a sub-subdomain of a domain I own (so instead of mycomputer.lan I’d have mycomputer.home.mydomain.tld). That would make the names much longer but would protect me against some asshat buying .lan as a new gTLD.







  • True. Just this weekend I spent far too much time trying to get a printer to work again on Windows after its IP address got changed. In the end Windows refused to talk to the printer unless I removed and then readded the device from the Settings app, which prompted a reinstallation of the device driver. No, just changing the IP address in the device settings wasn’t enough; Windows insisted on the driver being reinstalled.

    Linux didn’t need reconfiguration; it just autodetected that the printer had moved.

    I’m not saying that Linux is without issues, not by far. But Windows has never been terribly “it just works” for me either. The closest to “it just works” was (aptly) OS X somewhere around Snow Leopard.