X Windowing System is used in XWayland still. ~~X11~~ Xorg is no longer needed. RIP ~~X11~~ Xorg, you served us well.
Edit: Thanks to the note in the comments. I obvously meant Xorg is no longer needed, which is the widely used implementation of X11 protocol. This always confuses the hell out of me.
With Wayland, programs still can't restore their window position or size. It sure would be nice if they could get basic functionality working.
Wayland is still incomplete, but that is besides the point I was making. X is still not dead, even living within XWayland, within Wayland. X11 is just one implementation of the X Protocol and XWayland is a new implementation.
Wayland itself is functional and working, just not 100% compatible to X11. The same could be said about X11, it would be nice if they could get some basic functionality working right; but they can't, and that is why we need to replace it with something more modern and better. I think Wayland is working on a solution for restoring window position and size.
When X was created, there was no compatibility needed. Wayland on the other hand is in a different position, where it needs to innovate, make it more secure and keep as much as possible compatibility to X11, DEs and window managers. It's just unfair to just say Wayland would not have basic functionality working. It also depends on the desktop environments and GNOME is often to blame for.
It will never be compatible with X because they are different designs. X relies on a central program (server) that accepts commands from programs. It is also a mess as it was built during the 80s for 80s hardware. It was expanded over time but you can only stretch the arch so far.
Wayland doesn't have a server. You desktop talks to the hardware and then the desktop accepts connections from apps.
GNOME catching a devious stray there for no reason
That does not seem to be a stray and yes there's definitely reasons to take potshots at Gnome. They still don't support server-side decorations. Everyone is absolutely fine with them not wanting to use them in their own apps, have them draw window decorations themselves, and every other DE lets gnome apps do exactly that, but Gnome is steadfastly and pointlessly refusing to draw decorations for apps which don't want to draw their own decorations. It'd be like a hundred straight-forward lines of code for them.
And that's just the tip of the iceberg when it comes to breakage you have to expect when running Gnome.
I generally speaking like most of the other things you say on lemmy, so I’m just gonna agree to disagree and move on. Have a nice day
Programs can't set position or size of windows, period, at most they can ask and then hope they don't get ignored and it's good that way. Window management is responsibility of the compositor, not of applications.
At least KDE has support for it that's about on X11 level, a proper-proper solution is still in the pipeline. And yes you're seeing right it's been there for four years.
Oh noooooooo not a single QOL feature
Of course apps can and do restore their window sizes. Don't spread misinformation
that's not basic funcionality
This is undesired behavior, it should be controlled by window managers not applications
I for one want my windows tiled and tabbed
I think you mean Xorg instead of X11.
Yes, you are right. I always get tripped up with this one. Xorg is the implementation of the X11 protocol.
Wayland kinda is an x.org project in the first place. AFAIK it's officially organised under freedesktop but the core devs are x.org people.
x.org as in the organisation and/or domain might not be needed any more, but the codebase is still maintained by exactly those Wayland devs for the sake of XWayland. Support for X11 clients isn't going to go away any time soon. XWayland is also capable of running in rootfull mode and use X window managers, if there's enough interest to continue the X.org distribution I would expect them to completely rip out the driver stack at some point and switch it over to an off the shelf minimum wayland compositor + XWayland. There's people who are willing to maintain XWayland for compatibility's sake, but all that old driver cruft, no way.
Wayland is freedesktop's project and freedesktop is Xorg's project. But you are kinda correct.
Wayland kinda is an x.org project in the first place.
Not really. Wayland is fundamentally different from Xorg. Otherwise we would not need Wayland and create X12. It's like saying mechanical hard drives are kind of Solid State Drives, just because they allow to do something similar. Even if the developers are the same, does not mean the technology is.
AFAIK it’s officially organised under freedesktop but the core devs are x.org people.
I'm not sure if this is correct. But let's assume this is correct. Why does it matter? If Wayland was developed by different people than those who maintain Xorg at the moment, would not change the fact that we need Wayland, because it is different and solves issues that cannot be solved with Xorg without rewriting it. And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).
And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).
That's precisely the point: All the devs got tired of it and started wayland instead.
X12 might happen at some point when wayland is mature, as in a "let's create and bless a network-transparent protocol so we might have a chance of getting rid of XWayland in 50 years" kind of move.
Freedesktop is X.org's group. X.org isn't going away.
No feelings either way, I started using X since the last millennium and have been on Wayland without problems (Gnome or sway, never anything more than integrated graphics card) for about four years now.
But I really wish there was an fvwm for Wayland. And Window Maker.
Why is CDE not on the list?
I have a feeling I will be on i3 for many many years given all the issues that I've had with sway.
Have you tried hyprland
Yes, I spent a while reading the documentation on how to pin workspaces to certain monitors only for hyprland to tell me that it is deprecated.
Also an issue I noticed is that you can't move floating windows between displays with the move left/right commands, move left/right moves the floating window to the left or right of the display and no more, meaning that the window gets stuck at the border of the display and doesn't move more.
Also I couldn't figure out how to make hyperland run several commands in a row with one keybind, or how to filter windows with expressions, something that I do a lot on my i3config .
And my biggest issue, and this one seems to be with wayland in general is that it seems that it is impossible to set my displays to extended more, that is turn the 3 displays that I have into a single display which I use with some games.
i3 isn't perfect either, I actually had to fork it and apply a patch that fixes and issue that I have that hasn't been merged yet either.
I will list all my issues with sway anyway, hopefully somebody out there notices it and fixes them:
https://github.com/swaywm/sway/issues/8000
https://github.com/swaywm/sway/issues/8001
https://github.com/swaywm/sway/issues/8002
https://github.com/swaywm/sway/issues/8191
And all these bugs are the result of less than 2 days in total of use of sway, there is likely more that I haven't run into.
I also had an issue that affected xfce4 apps, but that issue ended up being a dbus-broker issue that only happens on wayland for some reason lol
I have workspaces pinned to monitors in Hyprland and have none of the problems you mentioned. I use odd numbers for left screen and even numbers for right.
Edit: just took a look and can't find mention of the depreciation; where did you read that?
hyperland itself told me that, I have a terrible picture (I didn't setup screenshots lol) of it: https://imgur.com/a/fWwmt1e
This was right before yuzu closed down btw.
and have none of the problems you mentioned.
You can move floating windows between displays with the move left/right commands? (not the move to workspace commands).
edit: Found a related issue https://github.com/hyprwm/hyprland-wiki/issues/242
That's just the way you write the rules being deprecated, not the functionality.
There is move left/right within a workspace, move to specific workspace and then move to next/previous workspace (from memory using e+1 as the workspace name in the command but might be misremembering). Admittedly this isn't exactly the same as what you want; I replied from my mobile and checked when I went back to my desk. I usually use meta/shift/[num] to send to a specific workspace though as I make heavy use of them.
That’s just the way you write the rules being deprecated, not the functionality.
I didn't say that it is impossible to do it, just that after I read the documentation it told me that.
Something that I couldn't even find in the documentation was how to do several actions with one keybind, on i3 each action is separated by a comma and you can assign variables to them, for example:
$BIND $MOD+$SHFT+Mod2+KP_1 $MVTO $WS1, $WS1, $WDUNST "$WS1"
Which means:
bindsym Mod4+Shift+Mod2+KP_1 move container to WorkSpace "1", WorkSpace "1", --no-startup-id dunstify -r 33 -t 600 "$WS1"
In english that is move the focused window to workspace 1, focus workspace 1 and send a notification of the current workspace (the last one is for some visual feedback).
### Multiple binds to one key [](https://wiki.hyprland.org/Configuring/Binds/#multiple-binds-to-one-key)
You can trigger multiple actions with one keybind by assigning multiple binds to one combination, e.g.:
# to switch between windows in a floating workspace
bind = SUPER,Tab,cyclenext, # change focus to another window
bind = SUPER,Tab,bringactivetotop, # bring it to the top
The keybinds will be executed in the order they were created. (top to bottom)
Oh it's done by assigning the same keybind to each action.
That will likeky make my config 1000 lines long 😅
Openbox here kek
Straight Outta Compton.
Where's my upstream explicit sync lads
Should all be in place. Even nvidia driver support. It's one of the rare cases where I actually support nvidia on a technical level, that is, having explicit sync is good. I can also understand that they didn't feel like implementing proper implicit sync (hence all the tearing etc) when it's a technically inferior solution.
OTOH, they shouldn't have bloody waited until now to get this through. Had they not ignored wayland for a literal decade this all could've been resolved before it became an issue for end-users.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0