Earlier quoted context omitted.
The claim was "shopped around" and if you are going to change people's words do not be surprised when nobody takes your challenge. And preemptively: absence of evidence is not evidence of absence.
> absence of evidence is not evidence of absence After holding up well for a long time, absence of evidence becomes a good indicator for actual evidence of absence.
Introducing stronger dependencies on systemd
171–179 of 179 posts
Re: Introducing stronger dependencies on systemd
#172Earlier quoted context omitted.
with 4.20, there is experimental wayland support for almost all xfce4 applications. I've used it and didn't even face a single crash. So, it's not far away.
great! Do you feel is a "good" change? does using a DE with wayland feels better or different? not talking about technical advantages...
Re: Introducing stronger dependencies on systemd
#173Earlier quoted context omitted.
Truly, don't bother. I've been watching this conversation play out for 10 years. I've watched it play out with systemd, udev, rust, Wayland. Just ignore them. Their validation is meaningless. Their ignorance is mostly meaningless, too, for reasons that feel mean to type out.
I'm getting the sense that both sets of parties here have a strong opinion and that this isn't a real discussion because of that.
I have worked on DEs, I have committed to compositors. I know which side has more merit.
Re: Introducing stronger dependencies on systemd
#174Earlier quoted context omitted.
> good tooling My completely oblique, binary logs disagree. It won because it solved problems companies with money needed solved. There is no indication that it succeeded on merit.
There are pros and con with binary logs. One isn't magically better. The tools they have for their logs are pretty good, and its incredibly easy to disable, if you do, you will never notice a difference. Helping engineers solve technical problems is not 'success'? Its only 'success' if open source nerds use it in their basement to run on an old sun workstation? What kind of dumb logic is that? Why do you think Linux…
Re: Introducing stronger dependencies on systemd
#175Earlier quoted context omitted.
Truly, don't bother. I've been watching this conversation play out for 10 years. I've watched it play out with systemd, udev, rust, Wayland. Just ignore them. Their validation is meaningless. Their ignorance is mostly meaningless, too, for reasons that feel mean to type out.
I'm getting the sense that both sets of parties here have a strong opinion and that this isn't a real discussion because of that.
Re: Introducing stronger dependencies on systemd
#176Earlier quoted context omitted.
The claim was "shopped around" and if you are going to change people's words do not be surprised when nobody takes your challenge. And preemptively: absence of evidence is not evidence of absence.
What does "shopped around" mean? That's not a common or accepted idiom for code. Or not one I've come across anyway. Also show me evidence of them "shopping around" code. I'll wait.
Re: Introducing stronger dependencies on systemd
#177Replying to some sibling comments asking why anyone wouldn't want to use systemd. People want to understand their software as well as it's practically possible. It's not an uncommon preference; worse-is-better was quite successful for a reason. As systemd stands, it's an unauditable mess of tightly-coupled components built to handle any conceivable need. These features create new attack vectors: for instance, systemd…
no longer…
https://catfox.life/2024/09/05/porting-systemd-to-musl-libc-...
Re: Introducing stronger dependencies on systemd
#178Earlier quoted context omitted.
Xorg was also a "good piece of software, foundational Linux infrastructure and very wildly deployed"
Still is?
Was just making the parallel with Wayland, how frustrating it has been for a lot of people, how everyone preaching correct software design, should be simple/protocols/standards/modular with correct responsibilities between projects... and how fast everyone forgot it
Re: Introducing stronger dependencies on systemd
#179Earlier quoted context omitted.
> no Wayland support yet That's not a downside.
My hardware doesn't work with X. Screen tearing. So im stuck with wayland, although I'd like to move to xfce when they support wayland
> xrandr --output DisplayPort-0 --set TearFree on
That works on AMD and Intel modesetting. There's something similar for nVidia. I haven't had a screen tearing issue in years on X11