[–] 20 points 8 months ago* (last edited 8 months ago) (3 children)

I'm so tired of reading this stupid argument. "People only dislike systemd because they're afraid of change." No, there are plenty of other concerning issues about it. I could probably write about a lot of problems with systemd (like the fact that my work laptop never fucking shuts down properly), but here's the real issue:

Do you really think it's a good idea for Red Hat to have total control over the most important component of every mainstream distro in existence?

Let's consider an analogy: in 2008, Chrome was the shit. Everyone loved it, thought it was great and started using it, and adoption reached ~20-30% overnight. Alternatives started falling by the wayside. Then adoption accelerated thanks to shady tactics like bundling, silently changing users' default browser, marketing it everywhere and downranking websites that didn't conform to its "standards" in Google search. And next, Chrome adopted all kinds of absurdly complex standards forcing all other browser engines to shut down and adopt Chrome's engine instead because nobody could keep up with the development effort. And once they achieved world domination, then we started facing things like adblockers being banned, browser-exclusive DRM, and hardware attestation.

That's exactly what Red Hat is trying to pull in systemd. Same adoption story - started out as a nice product, definitely better than the original default (SysVInit). Then started pushing adoption aggressively by campaigning major distros to adopt it (Debian in particular). Then started absorbing other standard utilities like logind and udev. Leveraging Gnome to push systemd as a hard dependency.

Now systemd is at the world domination stage. Nobody knew what Chrome was going to do when it was at this point a decade ago, but now that we have the benefit of hindsight, we can clearly see that monoculture was clearly not a good idea. Are people so fucking stupid that they think that systemd/Red Hat will buck that trend and be benevolent curators of the open source Linux ecosystem in perpetuity? Who knows what nefarious things they could possibly do....

But there are hints, I suppose. By the way, check out Poettering's new startup: https://news.ycombinator.com/item?id=46784572

  • source
  • parent
  • context
  • [–] 4 points 8 months ago (1 child)

    It's mostly Gnome 2 frozen in time - there have been small improvements here and there, particularly in Caja (the file manager). I think that's great though personally, and use it on most of my machines.

    Wayland adoption has been slow, but it is getting there.

  • source
  • parent
  • context
  • It was developed and released during a time where people obsessed with touch interfaces thanks to deficient computing devices like phones and tablets. So many people were wholly convinced that these things were going to completely replace general purpose computing, so projects like Gnome, which were being run by Red Hat, had to follow along one way or another, though they probably did so willingly.

    In any case, I am SO glad those days are over. It was far, far worse than the AI hype that we have to put up with today.

  • source
  • parent
  • context
  • [–] 16 points 8 months ago

    I don't think you understand the implications of what you're suggesting.

    Forking a project as large as Gnome is a massive undertaking. Not only is it a lot of up-front work to implement the functionality, but you also have to stay up-to-date with all upstream changes, and there's likely at least a few Gnome developers that are paid to work on it full-time, so that is a lot to maintain. And not only do you have to build it for your own distro, but you also have to convince maintainers of other distros to adopt it as well and put it in their repositories, otherwise you have no community of users, which means no community of developers either.

    Forking Gnome is wildly impractical. It's not a feasible suggestion to make at all.

  • source
  • parent
  • context
  • Dear Google: we wouldn't have to do this if you weren't such a shit company.

    Oh, you weren't aware that you're a shit company? You legitimately believe you're a positive force for the world? Well that's your own damn fault.

  • source
  • I had the same idea to write my CV in Latex, but then realized it's not such a great idea. I wanted to keep it down to 2 pages, so I ended up having to do a lot of manual formatting (font size, margins, spacing), and the whole point of Latex is that you're supposed to let the typesetter do the formatting for you. So I switched back to Libreoffice.

    But if I had a long-form CV, ie. an academic-style CV where you list all publications, conference talks, etc. with no regard to length, then Latex would be ideal for that.

  • source
  • parent
  • context
  • I haven't read through the other responses in the thread, but I don't think it's the slightly old software that's the problem. I think it has more to do with using older kernels, meaning that the latest hardware won't always be supported (on the stable branch at least - there's always testing and unstable too of course which may have better hardware support).

    That may have changed with recent releases though - I haven't used Debian for several years now. But if your hardware is supported then it's a pretty solid choice.

    Some other people sometimes mention that Debian isn't as beginner friendly as Ubuntu or Mint, but my experiences have been similar to yours - I found Debian to more user-friendly than Ubuntu for example. Assuming that the hardware works of course - if it doesn't then it obviously is a worse choice.

  • source
  • view more: ‹ prev next ›