Is i3 a meme?

I'm currently running lxqt that uses 450mb of ram, I like that. Openbox is cool and all, but I'm starting to think that a tilling window manager would be cool to use. My question is: Are tilling wm, and specifically i3, just a meme/prank?

Attached: i3.jpg (917x463, 60K)

> thousands of man hour to make a tiling wm, to meme/prank people
I don't use or particularly like tiling wms but no, they're not memes. They were made for autistic people tho.

Some people prefer to carefully arrange their windows, they want their windows to have specific size and position on screen. Some people like when their windows are automatically arranged in a specific layout. Just try it and decide for yourself.

yes no maybe so why not give it a go

Attached: 1554002153736.jpg (683x1024, 264K)

really nice, efficient. use it with qutebrowser and you won't need to use a mouse nearly as often.

If you have the time to really play around with it and customize it to your liking, it's really good.

>i3
nice beginner tiling
>dwm
the final stage. you get 120mb or less on idle

i3 is nice, it took some time to get used to it but after getting used to it i can't go back

How much RAM i3 uses on idle? 120mb on dwm would be awesome

maybe only on weekends, I've been trying to run it on a VM since yesterday. First I've installed ubuntu mini and i3, but for some reason the vm was extremely slow to uncompress things on apt, even giving it more threads. then tried lubuntu that already has some stuff that I would need, like compton, preinstalled to avoid that slowness on apt, ran i3 for a while, I've changed the colors and than I've started to notice some weird glitches when opening windows, I don't know how to explain, some kind of zigzag, whitenoise distorted graphics for a fraction of a second while opening and closing (just on that window, not on the entire screen), I had this thing when running gnome shell, I fucking hate when this happens. Maybe it's a bug on i3 that comes in 18.10 repos, next I'll try to install i3-gaps from git and see if this happens again. Can't install on the physical machine if it keeps happening