I like the idea of tiling window managers but never got the use for it. 99% of my time is spent between my browser, my IDE and my terminal. A half-size browser is painful to work with, I need it full screen. Same for IDE. Same for terminal, I do need multiple terminals but I want them together. I also have another workspace for chat stuff (browser with whatsapp, slack, messenger) and another for random apps (spotify…
Sway 1.0
101–110 of 256 posts
Re: Sway 1.0
#102I like the idea of tiling window managers but never got the use for it. 99% of my time is spent between my browser, my IDE and my terminal. A half-size browser is painful to work with, I need it full screen. Same for IDE. Same for terminal, I do need multiple terminals but I want them together. I also have another workspace for chat stuff (browser with whatsapp, slack, messenger) and another for random apps (spotify…
Re: Sway 1.0
#103Earlier quoted context omitted.
You're missing the point. Sway is a team of people working on their own time out in the open to create something they really care about for almost no money. The final product is staggeringly good compared to a commercial OS like macOS, and yes, tiling WM requires more up front investment and isn't a normal pattern for most folks, but that shouldn't make people feel like Sway or tiling is beyond them.
But they aren't making an OS. They're making a window manager. Why are you comparing a WM to an OS?
Re: Sway 1.0
#104Awesome! Fantastic news. If there's any chance sircmpwn is lurking here, quick question: has there been any further development on IME support? I use Mozc+IBus. Last time I tried on sway it almost worked, but the prediction box didn't show. That was the only gripe I had with sway. It solved all my tiny issues with i3 and made config much nicer too. Certainly making the switch if IME is better (or if I can easily help…
はい、Swayでibus+anthyはできます。Mozcはできないと思いました、でも今から変わったが可能性です。Swayを楽しんで!
Re: Sway 1.0
#105For a long time Xorg/i3 user, are there visible improvements when switching to Wayland/sway?
What is this about? The look of i3-gaps is extremely undesirable to me. Is it easy to avoid the look of i3-gaps?
Re: Sway 1.0
#106Earlier quoted context omitted.
> it puts macOS, built by Apple's army of engineers and dump trucks of money to shame I don't really think they're designed for the same purpose or audience, so I don't think it shames the Apple engineers.
You're missing the point. Sway is a team of people working on their own time out in the open to create something they really care about for almost no money. The final product is staggeringly good compared to a commercial OS like macOS, and yes, tiling WM requires more up front investment and isn't a normal pattern for most folks, but that shouldn't make people feel like Sway or tiling is beyond them.
Re: Sway 1.0
#107Earlier quoted context omitted.
I could equally state that overlapping windows are not a good default for everyone or every device type. It's also worth pointing out that Apples newest UI, iOS, uses a tiling window manager.
Tiling window managers were tried early on, when PCs were introduced. They failed because normal people didn't like them. Also, mobile OSes won't really ever have more than 2-3 windows shown at the same time, since the screens are so small. That will probably change once we have folding devices or AR/VR. But super limited "tiling" window managers do make sense with such limited UIs.
Do you have proof of this? I suspect they failed because everyone decided to copy the Mac which was trying to emulate a real desktop with bits of paper on it.
> Super limited "tiling" window managers do make sense with such limited UIs.
They also often make sense for complicated UIs, e.g. IDEs such as Visual Studio and browsers such as Firefox, which have docked sidebars and tabs in preference to overlapping windows.
Re: Sway 1.0
#108Is there an update to the nvidia (proprietary drivers) situation with sway/wayland?
The author still flat-out refuses to support them. This might change if Nvidia open-sources their drivers, which I suspect is part of what he's trying to do.
Nvidia refuses to support GBM, a standard way of allocating memory for graphics. Either they refuse this out of spite, or (more likely) because it fundamentally doesn't fit the architecture of their closed source driver. They are so desperate to push their alternative, EGLStreams, that they have lobbied Gnome and even created patches for KDE to be able to run Wayland on these DEs. This is not some closed source vs open source thing, since AFAICT the closed source Mali driver seems to support GBM and Wayland implementations that need it.
Therefore, the problem isn't that Sway doesn't support Nvidia. The problem is that that Nvidia doesn't support the standard ways to do graphics on Linux. This something Nvidia can in principle remediate themselves if they want it enough.
Re: Sway 1.0
#109Earlier quoted context omitted.
So you want to go to an app. You just hope that some corner is peeking out of that huge unsorted pile of windows. You call that good UX or is it just a formed habit?
Precisely. I arrange them such that I can click in the corner I need to get what I want, and then alt-tab between them, or click for the specific one I want if I need to jump. Then I get big real estate, and easy access. I call that good UX because it works well for me.
edit: You can also use something like rofi to fuzzy search for windows and quickly jump to them, instead of alt+tabbing.
Re: Sway 1.0
#110For a long time Xorg/i3 user, are there visible improvements when switching to Wayland/sway?
> Sway includes the features of the i3-gaps patches What is this about? The look of i3-gaps is extremely undesirable to me. Is it easy to avoid the look of i3-gaps?