4 ms·
That's quite a disingenuous response to something I said with citations and no direct stated opinions on the person. Be better
by CursedSilicon 1mo ago
That's quite a disingenuous response to something I said with citations and no direct stated opinions on the person.
Be better
- S-E-P 1mo ago> Be better What year are we in?
- CursedSilicon 1mo ago...Did we suddenly abandon bettering ourselves in 2026?
- S-E-P 1mo agoThe "be better" comment was used exclusively by the worst people i knew for 4 years straight. So for me, absolutely. It's condescending, unnecessary, and it is a polarizing comment people who are miserable leave to annoy the rest of us.
- CursedSilicon 1mo agoSorry that self-improvement hurts you so
- S-E-P 1mo agoSorry that you are incapable of seeing how others perceive you
- bmacho 1mo agoCitations from people who want the whole platform die. (Actually they get paid for that, it's their dayjob to kill X11, but it can be their personal belief as well)
- sertraline 1mo agoYep, it is important to remember Metux was a sole guy supporting Xorg for many years while everybody else outright refused to touch the codebase. Then they blamed Metux for "breaking compatibility." While this sounds like a plausible reason, long time Linux users could recall that every major X release broke something in one way or another. It's just how it is, there is no way around it. They blamed Metux for doing something that cannot be avoided while maintaining the project, and claimed that Xorg must burn. They also claimed features like namespaces would be impossible to implement in Xorg, which was later proven false as Xlibre brought XNamespaces -- as well as HDR and seat management. :) I'm personally a Wayland user because I have AMD iGPU and use whatever comes by default, but I couldn't imagine Nvidia users having the same experience as me, even with their new drivers. I know it sucks because I used to own Nvidia. Removing Xorg while Nvidia users make up the majority is insane.
- Timon3 1mo agoIIRC they blamed Metux for unnecessarily breaking BC, e.g. renaming & moving around symbols when it wasn't necessary and didn't improve features or fix bugs. When you're working on something this foundational, BC breaks should always have a good reason, and he repeatedly didn't give any. This causes churn for all downstream consumers. > It's just how it is, there is no way around it. There literally is a way around it: not doing unnecessary BC breaks.