1. 4

    I do try sway once in a while.

    The last time was the first one I was able to use if for a few days without major issue, but I went back to i3 on the next boot.

    The graphics seem sluggish with it relative to Xorg+i3, and it was thus uncomfortable. Maybe the next time, or maybe once I have a workstation again; Integrated graphics is a bottleneck.

    1. 6

      How long ago was this? Sway has been my daily driver for the last few years, both with Intel integrated and AMD graphics, and I’ve only had similar when not better performance in that regard. The main issue I encounter is compatibility with niche applications.

      1. 2

        Sometime between March and now. Not sure when.

        I will no doubt try Sway again, but one attempt per year or so is enough. Gives the whole stack time to mature and make a difference.

        For contrast, the previous time I had tried it, I gave up and returned to i3 within two hours. A few days is a lot of progress.

        Hardware on latest attempt is Ryzen 3700U (lenovo x395). The attempt before that, Haswell i7 with vega64.

        1. 1

          VMWare workstation has killed each of my attemtps to switch to sway over the past 3 years.

        2. 3

          What’s sluggish about it? It works well for me with the latest Mesa on an IVB CPU/GPU, which is ~8 years old now? There’s nothing sluggish about navigating Sway, and there’s no video tearing!

          1. 2

            It works well for me with the latest Mesa on an IVB CPU/GPU, which is ~8 years old now?

            Good for you. It doesn’t in my Ryzen 3700U laptop, bought mere months ago.

            There’s nothing sluggish about navigating Sway

            Instant switching between workspaces on i3, sluggish on Sway.

            and there’s no video tearing!

            It’d be sad if there was, since wayland’s designed with emphasis on eliminating tearing.

            1. 5

              Instant switching between workspaces on i3, sluggish on Sway.

              Interesting, I’ve had the exact opposite experience. When I ran i3 with a compositor, after switching workspaces, and application which uses OpenGL (including Firefox) would take a few tenths of a second before they showed up (the workspace would switch, but some of the windows in the switched-to workspace would pop in later). On Sway, it is always instant.

              Sucks that it doesn’t work as well for you.

              1. 3

                Same experience, for whatever it’s worth. I switched to Sway on my Pinebook Pro specifically because switching workspaces felt so instantaneous compared to any X11 WM.

                Looks like the 4700U uses the AMD Vega architecture for its GPU, which was released in 2017. I’ve had some definite teething problems with new AMD hardware on Linux, but usually the big issues are fixed pretty quickly. I’d definitely consider this a bug and report it to either Sway or Mesa, would be interesting to see what they say.

                1. 3

                  Discrete GPU, perhaps?

                  I suspect Wayland generally works better with plenty of vram. Or, conversedly, that it struggles with little vram. To do with composition, and keeping too many graphic buffers.

                2. 3

                  Good for you. It doesn’t in my Ryzen 3700U laptop, bought mere months ago.

                  If you’re using Mesa, then report it.

                  1. 1

                    Report what? That Sway is slow? Xorg works fine.

              2. 3

                Just as curiosity, were you using lot of applications which run under Xwayland? For me switching between workspaces is fast, but X applications (on my setup, few electron applications) take while to rerender, thus feeling slow.

                1. 2

                  I do indeed run a lot of applications, typically spawning 7 to 10 workspaces.