Better than you think. Every other time or so I log in in Gnome Shell in Wayland mode.
Thanks to xwayland you can run the majority of X.org applications without much problems in Wayland. The major problem with Wayland nowadays is bugs (I remember crashing my desktop trying to run mpv with Wayland native output, however OpenGL+GLX backend seems to work) and missing features (mainly touchpad support that is still treated as a mouse, or no touch support at all).
However running a Wayland setup has its advantages too, mainly improved composite performance in Gnome. No more screen tearing or skip frames of animation.
Thanks :) Things are mostly stable. Sway doesn't quite have all the features of i3, but it's getting there, and for bonus points it reads your i3 config file and interprets it correctly. I have trouble with floating windows, but if I wanted those I'd be using a different WM.
Probably my biggest complaint is that pretty much all of the graphical applications I use behave a bit oddly under Wayland because they're actually X applications running in XWayland. I spend most of my time in terminal emulators anyway, so it's not a huge deal.
Firefox and Chrome currently do not work on Wayland without Xwayland. But Libreoffice and Gnome work. You also have to use open source drivers for Wayland to work, so no Steam.
IPC
i3 has an IPC interface (it creates a socket that applications can connect to and issue commands or queries via its protocol), and sway replicates that protocol (so e.g. i3-msg can be used with sway by simply changing the socket, e.g. i3-msg -s $(sway --get-socketpath)). The code for that lies in sway/ipc.
No D-Bus in this day and age?
(not to undermine the otherwise impressive achievement, I was just a little surprised about this little backward bit. But then, I guess it's required for compatibility?)
Not using dbus for its ipc is a feature of i3 for me. What it has works perfectly compared to every interaction I've ever had with dbus, which is always pain.
Yeah i can't help wonder if dbus is one contribution element to making bluetooth painful on Linux.
This because the tray side client talks to the daemons over dbus to get anything done. And i have seen file transfer after file transfer get lost in dbus limbo.
By this i mean that i initiate a transfer from pc to phone via the gui. Everything checks out on both ends, but no data gets transferred.
So i hit abort, and try over, but now nothing happens at all.
And no restarting of the relevant daemons or clients change a thing.
Only by restarting dbus, and thus restarting my desktop along with it, will i be able to initiate a new file transfer (that may again get stuck in limbo).
i3 explicitly had a IPC interface separate from D-Bus:
"Implement an IPC interface for other programs. Provide subscription to certain events and accept commands.
This approach should be more lightweight than wmii’s usage of the 9P filesystem. Furthermore, core functionality does not depend on a separate program, so that i3 runs faster, especially when your system is under load."
https://i3wm.org/
I remembered this name from some place, then I looked at his github account and remembered he was the guy doing a cleanroom rewrite of minecraft. Amazing to go from that to working on this.
Considering the goal, which is stated very clearly in the README that's shown on the project page, that's not an out of line reply. Here's the first two paragraphs.
A completely clean-room implementation of Minecraft beta 1.7.3 (circa September 2011). No decompiled code has been used in the development of this software. This is an implementation - not a clone. TrueCraft is compatible with Minecraft beta 1.7.3 clients and servers.
I miss the old days of Minecraft, when it was a simple game. It was nearly perfect. Most of what Mojang has added since beta 1.7.3 is fluff, life support for a game that was "done" years ago. This is my attempt to get back to the original spirit of Minecraft, before there were things like the End, or all-in-one redstone devices, or village gift shops. A simple sandbox where you can build and explore and fight with your friends. I miss that.
Be careful googling for "Sway" and "Wayland" while at work... You might not get the screenshots you're expecting, although they will probably be shiny.
I did yet another quick search for "wayland remoting" and there still does not appear to be a well-supported story, so for me it's not even worth trying yet. In the age of IaaS and containers, who has just one computer?
It seems to me that something like xpra should be fairly easy to port to wayland. (For those who don't know, xpra installs itself as a compositing window manager, and then can render each window either locally or remotely).
Mostly usable unless you use nVidia or AMD with the binary drivers. AMD are going to be supported in the near future via their open-source amdgpu driver (for GPUs from 2015 onward) and nVidia will show up with a new driver that will support Wayland, any day now, we "promise".
So glad this is to make i3 work under Wayland. I jumped around with Tiled Window Managers for several years and it stopped 3 years ago when I started using i3. i3 has the best config system out (it reminds me of the old Arch rc file).
Once I saw this, I tried to use Wayland on an Arch Linux install. It worked great (apart from the really gross default cursor), until I tried to use gdm as my login screen. I have a two-screen setup (which worked fine with Sway if I just started it by itself). But if I start sway through gdm, the two screens would fuse into one screen. Is there any way to fix that? I'm guessing it's not a Sway issue, it's either an issue with the compositor Sway uses or just gdm.
Readit News
Dead Comment
Thanks to xwayland you can run the majority of X.org applications without much problems in Wayland. The major problem with Wayland nowadays is bugs (I remember crashing my desktop trying to run mpv with Wayland native output, however OpenGL+GLX backend seems to work) and missing features (mainly touchpad support that is still treated as a mouse, or no touch support at all).
However running a Wayland setup has its advantages too, mainly improved composite performance in Gnome. No more screen tearing or skip frames of animation.
Probably my biggest complaint is that pretty much all of the graphical applications I use behave a bit oddly under Wayland because they're actually X applications running in XWayland. I spend most of my time in terminal emulators anyway, so it's not a huge deal.
(not to undermine the otherwise impressive achievement, I was just a little surprised about this little backward bit. But then, I guess it's required for compatibility?)
This because the tray side client talks to the daemons over dbus to get anything done. And i have seen file transfer after file transfer get lost in dbus limbo.
By this i mean that i initiate a transfer from pc to phone via the gui. Everything checks out on both ends, but no data gets transferred.
So i hit abort, and try over, but now nothing happens at all.
And no restarting of the relevant daemons or clients change a thing.
Only by restarting dbus, and thus restarting my desktop along with it, will i be able to initiate a new file transfer (that may again get stuck in limbo).
"Implement an IPC interface for other programs. Provide subscription to certain events and accept commands. This approach should be more lightweight than wmii’s usage of the 9P filesystem. Furthermore, core functionality does not depend on a separate program, so that i3 runs faster, especially when your system is under load." https://i3wm.org/
It just is designed for scriptability: http://i3wm.org/docs/ipc.html.
Good luck.
https://github.com/SirCmpwn/TrueCraft/issues/230
A completely clean-room implementation of Minecraft beta 1.7.3 (circa September 2011). No decompiled code has been used in the development of this software. This is an implementation - not a clone. TrueCraft is compatible with Minecraft beta 1.7.3 clients and servers.
I miss the old days of Minecraft, when it was a simple game. It was nearly perfect. Most of what Mojang has added since beta 1.7.3 is fluff, life support for a game that was "done" years ago. This is my attempt to get back to the original spirit of Minecraft, before there were things like the End, or all-in-one redstone devices, or village gift shops. A simple sandbox where you can build and explore and fight with your friends. I miss that.
To add support for 1.8 is entirely out of the scope of the project.
Dead Comment
I'm feeling left out and perhaps a bit boring.
Deleted Comment