791–800 of 892 posts
Earlier quoted context omitted.
At least between-app DPI inconsistency was not a thing before this. Now its a thing, added to the stack of configuration problems.
If you support multiple DPIs then that will always be an issue, regardless of what display server you're using.
Earlier quoted context omitted.
There are not enough developers to even create a new release or review contributor patches. The Wayland community contributes a fair share due to xwayland, and we get stuck on this quite often. And yeah, it'll need fixes. over time. It's big, complex, and interacts with device drivers that are very much in flux.
I'm a bit confused about your post. Why would Xorg users care about XWayland, or new releases or contributor patches? Those who contribute to Xorg and feel stuck could step up to maintain it, if they wish. (Don't they do it already?) If they don't wish to maintain it, maybe their contributions are a waste of everyone's time? (Then again, maybe they get paid to do it, in which case it's their money-misery trade-off to…
XWayland is Xorg. An Xwayland fix is an Xorg fix. An Xwayland bug is an Xorg bug.
> Those who contribute to Xorg and feel stuck could step up to maintain it, if they wish. (Don't they do it already?)
No one maintains Xorg anymore, so there is no one to review patches, merge and roll new releases with them.
There's a huge difference between wanting to fix a bit and becoming an upstream maintainer.
The maintainers left for good reason, and no one wants to be stuck with that turd.
> Then, I'm sure someone will step up.
It is not "over time", it is now or never.
Earlier quoted context omitted.
There needs to be a better way to discover random stuff like this.
What are you hoping for? Someone to drop down and teach you how to do everything on wayland? I have no idea how to do keyboard automation on X11 but that says nothing about X11. This is the problem the post is talking about. Every single thread about wayland is filled with “but it can’t do Y” when it is possible to do Y.
Earlier quoted context omitted.
That's a legal disclaimer designed to head off a specific commercial legal liability. If you go looking to use law as a foundation for right and wrong, you're going to be sorely disappointed.
What I quoted isn't a law, this is something that authors have to deliberately put in their licenses/contracts for the specific work in question. If you wish to have other obligations with your open source software that you believe are less wrong, it would be wise to get those in writing.
I agree with that, projects should clearly state their goals and priorities upfront. But relying on legalese from MIT license is not the solution.
Earlier quoted context omitted.
One example is a tree. We are looking at a forest.
Not really, AFAIK this is the only part of systemd that really caused an issue, and it was because this is a capability that really needs to be provided by the OS and can't realistically be maintained as part of a desktop environment.
- Audio system that ignores all the foundations of ALSA and builds Yet Another Layer instead of improving ALSA.
- Display system that leaves way too much as an "exercise for the reader".
- 10+-year-long transition periods on the above, during which nobody's use cases work well.
- Decisions made by fiat rather than by consensus.
Earlier quoted context omitted.
> Look, if it's ok to say don't buy nvidia graphics cards and expect to use Wayland, why is it not ok to say don't buy mixed DPI and expect to use X11? It’s still a hard sell when everything just works on Windows and macOS. It’s yet another reason why someone won’t pick up Linux when 90% of the features they want are present.
People complain about mixed DPI all the time on macOS and Windows too. It works better, but it still doesn't just work. If you want things to just work, you'll have less fiddling to do if you get similar DPI monitors.
On windows I just plug my external monitor with regular DPI and it auto-recognize that this external monitor have regular DPI and size it acordingly while keeping the HIDPI of my laptop perfectly untouched and also auto recognized.
While on xorg, goodluck with that.
On Wayland it works, but require manual intervention of enabling fractional scaling and setting everything manually.
Earlier quoted context omitted.
Why does this distinction matter? Gnome on X works perfectly fine, Gnome on Wayland does not. Why does it matter it to state that Wayland is a protocol, not the implementation?
That's funny, because for me, it's exactly the opposite. I use Gnome on Wayland/Mutter and it works great - I've never had a linux desktop that had such great UI rendering. Gnome on X doesn't work and is buggy - it's riddled with graphical glitches that other platforms (even smartphones and tablets) don't suffer from. How can that be considered to "work"? But my requirements are different from yours.
Earlier quoted context omitted.
I'm beating a dead horse at this point, but there's no such thing as "switching to Wayland". What most people mean when they "switch to Wayland" is that they're switching from Gnome on X11 to a "pure Gnome" stack that uses Wayland and a bunch of other Freedesktop standards for interopability. There is absolutely no code from the "Wayland project" running there, because the Wayland implementation is Gnome's own (it's…
When I'm at my framebuffer terminal, I can either type 'startx' or 'sway'. If I go from typing 'startx' to typing 'sway' does that count as "switching to Wayland"?
Wayland is the implementation detail in Sway to have a display protocol your Gtk, Qt and XWayland apps use to draw themselves, really no need to draw more attention to it than necessary. It's the Sway implementation that does all the magic.
Earlier quoted context omitted.
Imagine this: Microsoft demands that Nvidia uses WDDM for their drivers. Otherwise DirectX would not work with Nvidia. Do you thing Nvidia would ignore them, like they ignore Linux?
M$ would probably pay nvidia. Does linux pay nvidia?
On some platforms (Mac) they don't have that opportunity at all.
Earlier quoted context omitted.
Interesting, but if you really are enthusiastic about the pinephone than perhaps try to order another motherboard (I’m thinking about it because the older has only 2 GB of ram)
I've got the Manjaro CE version, so it should be new enough. I'm also not flush wish cash, so... Yah, I'll be buying diapers for my toddler, not a motherboard that may or may not work. It's a shame, 'cause I really like the concept, and bought it for myself as a birthday gift. Thought it would be a fun project to hack on.