Earlier quoted context omitted.
Don't know when it was added, but I recently found out that you can have multiple synchronized Word windows of the same document.
On different people's screens?
Why don't we have Wayland on Raspberry Pi yet? (2018)
151–160 of 259 posts
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#152Earlier quoted context omitted.
So I'm no expert but I believe there are actually two different notions of hardware acceleration at play here: 1) HW accelerated rendering in Firefox, which despite being unfortunately disabled by default on linux can in my experience be enabled (on about:config) without issues. This makes the experience of scrolling much smoother, so I usually do that. I don't think this has any observable effect on battery life for…
I've used chromium-vaapi on Linux with some success. I don't think those patches have been accepted in upstream chromium though.
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#153Last time (which was when Fedora first shipped it by default) I looked at Wayland, it took me less than an hour to run into several showstopper issues and move right back. The ones I remember include being incompatible with the proprietary Nvidia drivers (and no plan to ever fix that), huge input lag (apparently stemming from the, um, "interesting" idea to make the compositor responsible for all input) and lots of ra…
> incompatible with the proprietary Nvidia drivers (and no plan to ever fix that) I've heard that Nvidia is fixing this in KDE Plasma and maybe Gnome too. (Fuck proprietary drivers though, and fuck Nvidia.) > huge input lag that's odd. Gnome's compositor is not the fastest, but it generally works okay for many many people. > the reasons one should consider a switch nowadays - No screen tearing ever, every frame is pe…
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#154Earlier quoted context omitted.
The bar for being important enough to not discard when it works and is the only solution to particular problems is not very high. I know of no other method to forward individual programs GUIs to other machines. Abandoning X is abandoning a power we have. You're right that it may not be used as much. Last time I used it was to debug why selenium tests running in chrome were failing in a server with a virtual display (…
I just use ssh/screen/emacs to work on remote servers. Why would I ever want an xterm?
With the fast networks we have nowadays performance is quite good.
I dread the time (if it ever comes) when Wayland takes over to the point that X11 won't be practical to use. And I would use EXWM too which would be even more painful.
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#155Earlier quoted context omitted.
Except that X11 isn't doing something so right -- it's still terrible, and it always has been, and we knew it was terrible at the time it was standardized. But it's funny that you would bring up something as terrible as a shell scripting language like bash to compare to how terrible X-Windows is. Have you ever read through a gnu configure file yourself, or do you just close your eyes and type "./configure"? Who in th…
> Except that X11 isn't doing something so right -- it's still terrible, and it always has been, and we knew it was terrible at the time it was standardized. And, yet, in ALL this time, not a single substitute arose? We have multiple web browsers, GUI toolkits, IDE's, etc. all with far larger codebases and yet X11 never got replaced properly. And some really brilliant minds worked on it. So the question you need to a…
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#156and
> Further slowing down progress is X-Windows. X is the graphical interface for essentially all Unix derived desktops (all other competitors died decades ago).
I'm confused. What's "X windows" and "X-Windows?" Is he talking about the X Window System?
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#157Earlier quoted context omitted.
I've been reading through the Vulkan spec, which is in way similar in that OpenGL has been extended since its introduction in 1992 with more and more features to support new graphics capabilities as they evolved. I've seen Vulkan called the successor to OpenGL, but reading the spec it seems more like the end game for raster graphics card programming. OpenGL 4.0 was released in 2010, and since then changes have been i…
Photoshop pretty much got it right a couple decades or so ago, and they've just been porting it, smearing on new lipstick, and figuring out how to make more money with it ever since.
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#158Last time (which was when Fedora first shipped it by default) I looked at Wayland, it took me less than an hour to run into several showstopper issues and move right back. The ones I remember include being incompatible with the proprietary Nvidia drivers (and no plan to ever fix that), huge input lag (apparently stemming from the, um, "interesting" idea to make the compositor responsible for all input) and lots of ra…
> incompatible with the proprietary Nvidia drivers (and no plan to ever fix that) I've heard that Nvidia is fixing this in KDE Plasma and maybe Gnome too. (Fuck proprietary drivers though, and fuck Nvidia.) > huge input lag that's odd. Gnome's compositor is not the fastest, but it generally works okay for many many people. > the reasons one should consider a switch nowadays - No screen tearing ever, every frame is pe…
I love nVidia's drivers. They "just work" and I don't need to muck about trying to understand why this version of this video driver doesn't play right with that version of drm or this kms setting.
Don't get me wrong, there are benefits to being a proper, native component of a modular display system. But what's the point if none of them work, only support random subsets of the hardware, and crash left and right?
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#159Earlier quoted context omitted.
Except that X11 isn't doing something so right -- it's still terrible, and it always has been, and we knew it was terrible at the time it was standardized. But it's funny that you would bring up something as terrible as a shell scripting language like bash to compare to how terrible X-Windows is. Have you ever read through a gnu configure file yourself, or do you just close your eyes and type "./configure"? Who in th…
> Except that X11 isn't doing something so right -- it's still terrible, and it always has been, and we knew it was terrible at the time it was standardized. And, yet, in ALL this time, not a single substitute arose? We have multiple web browsers, GUI toolkits, IDE's, etc. all with far larger codebases and yet X11 never got replaced properly. And some really brilliant minds worked on it. So the question you need to a…
Re: Why don't we have Wayland on Raspberry Pi yet? (2018)
#160Earlier quoted context omitted.
X is good enough for majority of the users, even if the architecture is not perfect.
The fact X11, as the "standard" windowing environment for Unix operating systems, was ditched by literally all major Unix operating systems created in the last 20 years like Mac OS X, Android, iOS, etc, tells us that X11 is not good enough. For example here is an Apple developer explaining why X11 wasn't chosen for Mac OS X: https://apple.stackexchange.com/questions/168980/if-os-x-doe... (By "Unix operating system" I…