Originally posted by kokoko3k
View Post
Announcement
Collapse
No announcement yet.
Firefox 75 On Wayland Now To Have Full WebGL, Working VA-API Acceleration
Collapse
X
-
Originally posted by Britoid View Post
You're confusing so many things here.
1) They're KDE Wayland bugs, they don't exist in Sway, GNOME etc.
2) Right, and X crashing won't bring down GUI apps either?
3) Remote desktop is working fine here.
4) Windows is not comparable. It has a display system where it's normal that applications could loose access to the compositor (graphics driver updates etc), and applications don't usually talk it directly. Additionally, on newer versions of Windows it shouldn't be possible to run without dwm without crashing.
- Likes 1
Comment
-
Originally posted by treba View Post
X11 is pretty much in maintenance mode already. Don't expect developers to invest much in it any more - it's just painful and the faster users switch to Wayland, the better.
Comment
-
Originally posted by birdie View Post1. KDE has major troubles working around Wayland which speaks volumes about Wayland APIs. It's not like KDE devs are stupid.
Originally posted by birdie View Post2. X.org has maybe crashed on me three times in my entire life. KWin and other window managers crash far too often and the system lives on. In Wayland a WM and a graphical subsystem are the same entity. That's absolutely wrong. Neither Windows, nor X.org was designed this way. How do you go about replacing your DM/WM in Wayland on the fly? Not possible at all?
Originally posted by birdie View Post3. Using experimental Pipewire? How fast does it work in comparison to ssh -X/RDP? Can you watch videos over poor connections? Can you pass-through OpenGL/any sort of HW acceleration? No, nothing? Oh, crap. Wayland works with raw rectangles made of pixels. It cannot even say which parts of an application need updates to be sent over the net and which don't. Each active application window needs to be encoded in its entirety and sent. Wow, such an utter crap.
Originally posted by birdie View Post4. Windows is always not comparable, only it offers vector very efficient GUI + video streams pass-through + Direct3D pass-through + audio compression and other perks. It was designed way before Microsoft even thought of remote desktopping yet they made it near perfect. Wayland designers perfectly got all the knowledge of the real world requirements and designed the protocol which is 100% ill-unsuitable for remote desktopping.
Originally posted by birdie View Post5. Wayland requires GUI APIs to handle raw output, scaling and font rendering and antialiasing as it does nothing itself. Let's say you have three applications running using three different APIs (Qt, Enlightenment, Gnome). Let's say the user wants to upscale all three or change font antialiasing for all of three. Wow, we have some crazy crap going on here as each GUI API has to independently implement these features instead of relying on one common API which does everything for them, e.g. Win32 or xlib (though honestly Xlib has long been abandoned and Xorg works in many ways close to Wayland nowadays since it wasn't designed to handle modern GUIs).
Originally posted by birdie View PostWayland is great, isn't it? And this crap will forever require XWayland which is just nice.
Originally posted by birdie View PostAnd XWayland applications cannot even properly interact with native Wayland apps. Tons of useful X.org utilities outright don't work under Wayland in any shape or form.
Originally posted by birdie View PostYeah, I'm trolling hard.
Originally posted by frank007 View PostWhere can I read that Xorg is in maintenance mode? This is their site: https://www.x.org .
- Likes 10
Comment
-
Don't know how much it's related, but you know what also doesn't help?: https://bugzilla.mozilla.org/show_bug.cgi?id=1561359 I mean, come on! It's been out since LAST JULY FFS!
- Likes 2
Comment
-
Originally posted by andre30correia View Postyour wayland is special!! can you play fps games too?
- Likes 5
Comment
Comment