• 1 Post
  • 83 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle


  • jsdz@lemmy.mltoLinux@lemmy.mlThe future of Linux
    link
    fedilink
    arrow-up
    21
    ·
    1 year ago

    Well okay, since it’s up to me: Let’s have free software. Fully free Linux on every phone, including all “firmware” which has gotten awfully soft lately. No more proprietary driver blobs for ethernet controllers or cellular modems. No more proprietary DRM modules. No more “smart” consumer goods that come without source code. The free software revolution has gone pretty well in some respects, but we need to finish the job and put an end to all that garbage.





  • It’s yet another scheme to gather data about Chrome users for the benefit of advertisers. Aside from the fundamental problems with that whole idea which people most often point to, it’s also underhanded in a way that cookies, tracking scripts, and browser fingerprinting aren’t: It’s code that’s built in to the web browser itself which exists for no purpose other than to act directly against the interests of its users. It may be the first time that’s happened in such an obvious and unambiguous way.


  • jsdz@lemmy.mltoLinux@lemmy.mlAnother post for not using systemd
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    1 year ago

    the packagers had not changed it as they were asked to do

    Were they really? Or were they told “change it if you don’t like it”? Genuine question, and it would make some difference.

    But in either case I’m sure not all of them did, and failing that it is all down to the one person (or worse, one team of people) administering the system. Badly configured networks resulting in DNS problems is not exactly rare, but that is beside the point. It’s clearly wrong no matter how uncommon is the situation that makes it materially detrimental.


  • jsdz@lemmy.mltoLinux@lemmy.mlAnother post for not using systemd
    link
    fedilink
    arrow-up
    4
    arrow-down
    4
    ·
    1 year ago

    It’s just one more annoying little thing to go on the big list of items to be corrected when setting up a systemd-equipped system, but more importantly believing that it’s acceptable to just leave it there demonstrates extremely poor judgement to a degree that makes many of us doubt the trustworthiness of the entire project. Perhaps in 2013, or whenever the decision was initially made, substantial numbers of people were sufficiently clueless as to think that adding in the possibility of inadvertently having your system quietly direct all its DNS queries to Google was better than the more obvious alternative of not doing so, but after everything that’s gone down since then it’s quite hard to imagine why anyone would stick up for such a bizarre point of view today.




  • jsdz@lemmy.mltoLinux@lemmy.mlAnother post for not using systemd
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    1 year ago

    monopolisation of the init system

    That’s the one thing about systemd that is sort of nice. We don’t really need to have more than one init system, and it does a sufficiently comprehensive job of being one. If it were only an init system and nothing else, there basically wouldn’t be any remaining complaints about it by now.