this post was submitted on 18 Jul 2023
336 points (84.3% liked)
linuxmemes
21180 readers
805 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
I have barely used them, so I’m not the best at explaining, but for me it boils down to a number of things.
First, TWMs are meant to work with keyboard shortcuts more than with any mouse input. Easy for those to conflict with the shortcuts of your app.
Second, compatibility might be an issue if your TWM doesn’t use a normal compositor. I don’t know how well something like Blender would render its UI on a TWM.
Third would be that a lot of creative apps are not meant to be tiled by the system and have their own solutions for window management, which could conflict with the TWM.
I’m sure there are more reasons. I can’t think of them just now.
That's persuasive! I'll stick with GNOME/KDE then. 😂