Why aren't you using the superior window manager Jow Forums?
Why aren't you using the superior window manager Jow Forums?
Other urls found in this thread:
youtu.be
youtube.com
terminal.sexy
twitter.com
dwm.exe
because there's Window Maker
>dynamic tiling
>poor keyboard controls
If you need something other than master-stack you're just an autistic ricer.
>>poor keyboard controls
>what is changing keybindings
I bet you installed it from the AUR
it’s ok
It cannot support window controls more complicated than alt+tab style cycling. And floating mode is basically mouse only.
you can patch it for full keyboard window controls
you can patch it for just about anything
until the patches start conflicting lol
haven’t had that problem with about 50 of them
is this actually dwm? what patches do you run?
Why might one prefer it over i3?
yes, a lot
minimalist autism, written entirely in c
You appear to be gay.
It's easier to use than i3 and follows the suckless philosophy.
it's fucking beautiful
thanks
>easier to use
in what world is dwm easier to use?
So how is that different from i3?
>follows the suckless philosophy
That sounds pretty vague (after reading the page), care to elaborate?
You don't have to think about arranging windows so they fit your perfect ricer autism. It just werks.
No complicated list of 60 keybindings either.
Oh my god you even lined up your browser with your wallpaper. This is real autism.
no i didn’t
It's minimalist, being less than 2000 SLOC and only 64 KB compiled on my system. Because of this it's really easy to extend and maintain it.
Their Philosophy page explains it pretty well. They're fighting against everything wrong with modern computing.
this
don't follow this it makes you suicidal
Did use it for several years and loved it, now I'm on fluxbox because of floating issues i had with a specific program and was too lazy to fix it on dwm.
>being less than 2000 SLOC
Well fuck. I'm trying to get into i3 hacking and their codebase is around 20k LOC. xmonad guys were proud to be under 1k LOC by using high-level Haskell, how the fuck did suckless guys get under 2k LOC in C?
>It's easier to use than i3
I beg to differ. What's with this master and stack shit? With i3, you're telling it, "I want the next window to go HERE" and it does that. How much more straightforward can you get?
Dwm v xmonad?
Here's a comparison of linux tiling wm's.
I personally like the way herbsluft wm works.
Follow it to a reasonable degree. Doesn't hurt to keep things simple. Just don't use links to browse the web.
I'd argue master-stack is more straightforward since you don't have to think about how your windows are supposed to be placed.
If you REALLY want to you can apply a bunch of patches to change this.
oh man i'm sure we would be really really good friends
>If you REALLY want to you can apply a bunch of patches to change this.
or I could just use a decent WM
Relevant
placing windows in certain positions is the main thing most people want from a wm
hacker one liners
I prefer floating WMs.
this + tmux
I was thinking that until I tried a WM that manages layout automatically. And it makes a lot sense, when you have only a few windows it doesn't really matter where they are as long as they are visible (you might make distinction between big primary windows and smaller secondary as well). Only when you have so many windows that they stop fitting on the screen is when the specific placement of windows matter. And i3 does have a very cool feature for that, that doesn't fit into automatic layouts: tabs (or stack which is the same shit).
Don't see xmonad there, I'm curious
>GHC spews out ridiculously large binaries
>GC
>expects it to fit on the scale
>binaries size
>main memory usage
Sorry user, I don't have a brainlet image for you. Have a lobster instead.
The size of the binary is related to the amount of memory a process will use, retard.
Currently running with tilegap, cfacts, mpdcontrol, no boarder and move stack. Pretty comfy
But not in a simple way. The reason why GHC spews out huge binaries is because it links everything statically so it can inline and optimize expressions. So that big binary size corresponds to libraries that would have to be loaded dynamically otherwise. Not trying to say that a GC'd language doesn't use much memory though.
Static linking throws the possibility of using shared memory altogether, so you should expect higher memory usage.
Because I am using xmonad
What does "dim" stand for?
>static linking is more bloat
user telling straight facts here
>t. seething sucklessfag
I don't suck more.
But i am op
But I am.
Because SwayVM requires better drivers than the crap Nvidia gives me.
>I only know freedesktop xorg
>I believe everything RedHat say
I believe what the X devs say, rather than armchair Jow Forumsers
youtube.com
That logo says dim
DWM is the Windows Vista and up compositor
Not that user but I have never met a programmer I respect who favors dynamic linking. Every single one I've met who is good at what they do and is dedicated to the craft see dynamic linking for the non-solution to a non-problem it really is.
Static linking is a good way to end up with major security problems.
Used both off and on. xmonad is pretty cool, but DWM does everything I need without the superfluous Haskell runtime.
> openssl bug
Oh shit, better rebuild all 2000 packages in my distro that link openssl. Better keep all my fucking object files too; there's probably going to be a ImageMagick bug next week.
It didn't solve the problems it was supposed to in the 80s or whenever, and it's definitely overused, but saying it's unnecessary is just wilfully ignorant.
>Your fortune
This put a smile in my face. Thanks user
Wmii was a way better.
>he fell for tiling meme
Edit source by hand using the patches as reference.
I've done it before, it's a hassle but if you've got some free time it's nothing.
what do your relatives think about you?
What they want maybe--but is it what they really need?
Because after compiling it, none of the key binds work. Awesome is better
I agree with this user. I love suckless but I can't use this dynamic stack shit. Started with i3 and got too used to moving windows around quickly and putting them where I want that it annoys me too much when it's automatic.
>using a gui
Tiling WM's are so fucking comfy, especially on laptops where you have no decent mouse.
But I am.
Looks nice but you suck at Tetris
Already am. Same name, but predates yours by a decade.
are you a fucking virgin
:^)
I'm doing it again
>doing it
proof
>not having a clitmouse
And actually there was one more thing I was wondering about: afaik binaries are lazily loaded so you don't load a chunk of code until you need it. And then if you don't use for a long time and you are at maximum memory capacity it will be swapped out.
I hate how st doesn't come with that awesome color scheme
Sweet lobster bro
i love my herbstluft
I prefer bspwm.
It's slow. Plus, I don't get the double borders stuff.
Choose st as the output
dwm is software designed to make computing harder. Having to dick around with patches and compiling instead of actually getting anything done.
>switch to dwm years ago
>add a bunch of patches for my autistic needs
>sits at 9MB now, ruining the minimalism meme
>no other wm is appealing enough to switch away from it
have I memed myself
YOU BLOATED UP YOUR DWM
KILL YOURSELF
GET OUTTTTTTTTTTTT
GO BACK TO Jow ForumsUNIXPORN
REEEEEEEEEEEEEEEE
dwm is supposed to be used without any patches
cos i use XFCE
but user my layouts and useless gaps
Because AwesomeWM exist.
My nibba
Show your 9MB dwm
We're talking purely about resource usage here, and dynamic linking will yield smaller memory footprint, because you can take advantage of shared memory. Static linking allows you to provide whatever version of a library you want, which in short term might help with reducing problems with tracking down the right libraries, but in long term you end up with binaries full of old and vulnerable library code. Pick your poison, I think I'd rather stick with dynamic linking and compile libraries once to update them for every compatible program.
get rid of the title bar you fucking mongoloid
I think most of it is the pertag stuff, on two screens so two tag sets, all the extra layouts (bottom stack left/right stack), and the extra resize options. might also be the stuff its compiled with like the xinerama stuff. regardless of that it still starts as fast as the regular dwm even on my slower machines