81–90 of 146 posts
Earlier quoted context omitted.
I assume it starts with showing you’re up to it by putting in the work. You don’t need to be the release manager to contribute patches.
But who will review your patches, if all the core devs have already moved on to Wayland?
The author uses Pipewire with WebRTC in Chrome, very cool. Pipewire is showing up all over the place. I've been reading a little about it, but I finally got a comfortable setup of jackd and pulseaudio and am worried it might interfere with my stable setup. Am I being paranoid?
The next version of fedora uses pipewire instead of pulse audio. From all the people I have seen test it, they said it works much better than pulse.
I was really looking forward to Wayland, when I moved to Linux. It was then said to be right around the corner. That was six years ago. If the current state of Wayland is as bare-bones as depicted in the article, it's just sad. And as there is no support for OBS on the horizon, it's a non-topic for me. And I never liked X11 to begin with...
Pipewire has the brightest future long term, but wlrobs seems to be the easiest to get started with if "Wayland" means wlroots based compositor (Sway, Wayfire, etc) in this instance.
- A unified way to change applications settings. All old X apps used to read the X resources database (xrdb): you could set a global color scheme, fonts, window geometry and what not, all in one place using a simple but powerful text format.
- The simplicity of the window managers, hotkey daemons and other X clients. You can implement a functional wm in a few hundred lines of C[1] because the X server takes care of most of the stuff. In comparison a compositor has much more work to do and it's difficult to implement one, unless using a big library like wl_roots.
- A base graphics API based on drawing primitives like the original X, SVG or Cairo, rather than just bitmaps. This would make writing a simple application without importing huge frameworks feasible again. Also sending the drawing calls over the network would probably be less bandwidth intensive.
Is it still the case that Nvidia drivers don't work with Wayland?
Earlier quoted context omitted.
The short version is "it depends". Essentially, each separate Wayland compositor needs to add support for the nvidia driver (or the driver needs to support more standardized APIs). Gnome and KDE support Wayland on nvidia hardware (though it's a bit rough around the edges). Wlroots (and therefore Sway) doesn't because they don't want to have a separate code-path for one driver which doesn't want to support standards a…
Nvidia works with wlroots if you use nouveau and not the proprietary drivers.
Is it still the case that Nvidia drivers don't work with Wayland?
I don't expect them to ever work properly. Basically, if you care about good Wayland user experience and proper desktop integration, you should be using AMD or Intel GPU already. Waiting for Nvidia to fix this mess is pointless. Nvidia will be DOA as long as they refuse to upstream their driver or to support Nouveau to begin with. And they didn't show any interest for years.
Earlier quoted context omitted.
CUDA is an industry standard, and AMD's lack of support is why NVIDIA enjoys a monopoly in the deep learning community.
Is this due to CUDA being a technically superior product, or is it just that it's entrenched? OpenCL/AMD is a usable and mature platform, right?
I have, however, seen attempts to use Vulkan for compute. Could that be a viable way forward?
Earlier quoted context omitted.
Besides security concerns, mixed-DPI setups are such a major pain point with X11 that many people who use a laptop with additional screens would probably switch to Wayland just for that alone. That's a large demographic.
Do any desktop system handle mixed DPI well? I mainly use Linux so I don't know, but one of my work laptops have windows on it and it freaks out every time I connect it to a 4k monitor. At least in linux I can use triggers and xrandr [1] to manage it even if it's not pretty, never figured out how to do it automatically in windows. Edit: I am using KDE/Qt apps for 99% of my gui stuff. Gnome etc might be worse. [1] htt…
MacOS handles it very well, moving a window from a high-DPI display to a low-DPI display works perfectly.
I'm not sure about how Windows handles mixed-DPI, but it handles DPI changes mostly OK. I only access my Windows machines via RDP, so sometimes they get a high-DPI display and sometimes they get a low-DPI one. Apart from one program (there are per-program settings available in Windows to help fix scaling issues) everything seems to handle it fine.
I don’t know how I feel about Wayland. On the one hand it’s being made by x11 devs so I think they more than anyone else know why they would need to start from scratch over improving x11. On the other hand, moving away from x breaks so many things and I haven’t heard anyone singing it’s praises yet about how happy they are to use it. I understand apps are breaking because they relied on features of x that were securi…
to benefit from every feature one has to run current software, as the ecosystem catches up. And as others write, AMD/Intel gfx have a better time than if you're on Nvidia.
Wayland as of writing has my use-cases covered: hw accelerated video decode in Browsers (FF and Chrome), Browser screensharing (via pipewire) and via VNC (conveniently surfaced to gnome-settings if gnome-remote-desktop is present). Most current distributions do not carry all necessary packages in their defaults last I checked, so one had to have some interest and flip one or two browser config flags.