| ▲ | yjftsjthsd-h a day ago |
| I'm mildly bemused at the other comments treating this as a blast from the past. I use icewm today as a super low resource DE for a headless remote desktop system, with a major benefit being that it's all in one with no configuration needed; one unit includes panel, app menu, and window manager that work out of the box. |
|
| ▲ | arexxbifs 20 hours ago | parent | next [-] |
| It can be both. I'm daily driving FVWM, which is even older than IceWM and still under active development. I'm fine with people thinking it's "retro", because it is. But mostly I'm happy I can still use it. Incidentally, tiling WM:s are even more retro, even if they're all the rage right now. GNU Screen and Oberon are both from 1987. |
| |
| ▲ | jjtheblunt 20 hours ago | parent | next [-] | | i used FVWM on my sparc Solaris and other unix workstations in the late 90s...awesome to see it's still actively developed. loved it. now i'm using hyprland as its configurability reminds me of being able to set up ergonomics in my own personally favored ways. anyway, just a data point after happily seeing your comment. | |
| ▲ | arcanemachiner 17 hours ago | parent | prev [-] | | I'm confused, isn't GNU Screen a terminal multiplexer? | | |
| ▲ | yjftsjthsd-h 14 hours ago | parent [-] | | screen is a terminal multiplexer that at some point added the ability to split the terminal in a tiling manner, but that's a lot more recent than 1987 |
|
|
|
| ▲ | mkovach a day ago | parent | prev | next [-] |
| I use it as my main DE for many of my systems, including my writing laptop. It is really, just as you say, pretty much install-and-use. At one time, I maintained a fairly extensive FVWM configuration, but trying ICEWM a few times freed me. |
| |
| ▲ | pluc a day ago | parent | next [-] | | That's fluxbox for me! https://fluxbox.org/ | | |
| ▲ | gen2brain 21 hours ago | parent | next [-] | | Yes, I used that a lot, I had some crazy configs there, mini TV in dock with XawTV or something, and nice panel. But for years I prefer Openbox, configured once and it just works. Today i also have Labwc, almost same experience, LXQt works fine with both. | |
| ▲ | interroboink 17 hours ago | parent | prev | next [-] | | I've been using fluxbox for a good decade-plus; in that time I've accumulated maybe ... 2 or 3 things to complain about? Suits me very well (: | | | |
| ▲ | mkovach a day ago | parent | prev | next [-] | | Fluxbox was something I tried. Icewm just tickled my fancy a bit more. Still solid. | |
| ▲ | augustk 21 hours ago | parent | prev [-] | | For me it's Blackbox. I really like the austere default gray theme. |
| |
| ▲ | Twirrim 18 hours ago | parent | prev [-] | | I might give IceWM a shot. I keep wanting the impossible. Something minimalist like i3, FVWM etc. but comprehensive, so I can go without what kept feeling like all the hassle of having to write custom utilities for so many operations and spending a lot of time having to configure the damn thing. |
|
|
| ▲ | networked 21 hours ago | parent | prev | next [-] |
| IceWM is a good DE for xrdp servers (https://en.wikipedia.org/wiki/Xrdp). This makes it my main window manager on a workstation I access through Remote Desktop. On my old ThinkPad, I had to migrate off IceWM because Xorg on Debian 13 no longer provided video acceleration. I have switched to Wayland and KDE. With IceWM, you need to take care of the SSH agent that KDE or Cinnamon would start for you. You can do it with something like this in your `.xinitrc`: # SSH agent
mkdir -p "$XDG_RUNTIME_DIR"/ssh
eval "$(ssh-agent -a "$XDG_RUNTIME_DIR"/ssh/agent)"
export SSH_AUTH_SOCK
# ...
# WM
exec icewm
|
| |
| ▲ | ErroneousBosh 20 hours ago | parent [-] | | Why would you use a desktop on a server? What's the use case there? | | |
| ▲ | networked 19 hours ago | parent [-] | | As I said, the computer is a workstation. The xrdp server is a server in the same sense as sshd. I access the workstation remotely from my laptop, iPad, Android phone, etc. I picked Remote Desktop over, say, X2Go because it had the best iPad client some years ago (Microsoft's own). | | |
| ▲ | ErroneousBosh 19 hours ago | parent [-] | | Ah, makes sense. I do something similar with Haiku and Apache Guacamole so I've got access to my dev box wherever. |
|
|
|
|
| ▲ | inatreecrown2 a day ago | parent | prev | next [-] |
| I use it as my main desktop for audio work. |
| |
| ▲ | fho a day ago | parent [-] | | I always wondered if that's worth it. I've been running a whole band (16in, 8out) with Ardour, 3x Guitarix and "standard effects" (EQ, Compression, Barry's Satan Maximizer, etc) for some years now on a 10th gen i7. That's with -rt patches and running live. I considered switching to Xfwm, but even with Gnome3 I never had issues with performance. | | |
| ▲ | inatreecrown2 a day ago | parent [-] | | I don't think its necessary for performance reasons, just a personal choice which one you like better. |
|
|
|
| ▲ | dead_hn_theory a day ago | parent | prev | next [-] |
| > treating this as a blast from the past. Well, for most of us it is. |
|
| ▲ | glenstein 19 hours ago | parent | prev | next [-] |
| I use it today for a Pinetab 2. I used it then, but I use it now, too. |
|
| ▲ | fasterik a day ago | parent | prev [-] |
| Why is it bemusing because you happen to have a use case for it? It's a 30 year old piece of software that only supports X11, which is itself rapidly becoming legacy software. |
| |
| ▲ | torstenvl 20 hours ago | parent | next [-] | | X11 is actively developed and it's here to stay, despite unearned vitriol, especially from those with conflicts of interest. | | |
| ▲ | 0x1ch 18 hours ago | parent [-] | | Is the conflict of interest in the room with us? Every major distribution has greenlit Wayland and introduced into their stable releases as the default. X11 is not actively developed, a fork is. | | |
| ▲ | necovek 18 hours ago | parent | next [-] | | > X11 is not actively developed, a fork is. That's a weird framing. Original X was forked as XFree86 and included in all the major distributions. Xorg was a fork of XFree86, and subsequently included in all the major distributions when some devs/sponsors wanted to take it in a different direction. XLibre — if that's what you are referring to — is another fork in a long line of forks. So when you say X11 is not being developed but a fork is, which one are you referring to? | | |
| ▲ | 0x1ch 17 hours ago | parent [-] | | Weird framing is injecting decades old semantics to an issue most people already understand as X11 vs Wayland. Since everyone has defaulted to X11/Xorg prior to Wayland, it is known as xorg and x11... Not that fork of "XFree86". X11 and Xorg, as we know it, are not in active development but maintenance mode. They have planned to wind down for a while, and this has been old news for over six years now... The code rollback and freeze inquiries should've signaled people off. |
| |
| ▲ | torstenvl 13 hours ago | parent | prev | next [-] | | You seem to be confused between X11 as a protocol (and, used loosely, its many implementations) and a specific X11 server. Within the Linux community, the primary X11 implementation has been the XFree86 server, which forked into XOrg over licensing disputes, which forked into XLibre over the development roadmap. Other implementations include XQuartz (also based on XOrg) and Xlibe (not a traditional server but implements X11 by translating into native Haiku graphics API calls). There's also Xming and android-xserver (written in Java!), among many others. XOrg may be abandoned. That doesn't mean the entire ecosystem is. | |
| ▲ | yjftsjthsd-h 18 hours ago | parent | prev [-] | | > X11 is not actively developed, a fork is. Xorg is not actively developed. X11 is fine. | | |
| ▲ | 0x1ch 17 hours ago | parent | next [-] | | Both are in maintenance mode? Red Hat and Canonical made their calls, and basically every other desktop environment outside of their control as well. Some were late, but are now here. Outside of legacy systems, I just don't see why people are going out of their way to get back on X11/Xorg outside of perceived FOSS politics and posturing. See - XLibre code of conduct and the Arch fiasco. | | |
| ▲ | yjftsjthsd-h 14 hours ago | parent [-] | | > Red Hat and Canonical made their calls, and basically every other desktop environment outside of their control as well. Thankfully, that's not really how open source ecosystems work. There are still people interested in both using and developing X11. > Outside of legacy systems, I just don't see why people are going out of their way to get back on X11/Xorg outside of perceived FOSS politics and posturing. Well, when Wayland supports the features that people use on X11 I suppose we can discuss it. As of the present day, moving "forward" to Wayland would mean massive regressions in a11y tools that I'm not willing to give up just yet, and accepting a fragmented landscape where questions like "how do I change the keyboard layout" or even "is it possible to change the keyboard layout to anything but us+qwerty" are "It Depends™, what compositor do you use" (because Wayland deeply believes in reinventing the wheel over and over again, forever). |
| |
| ▲ | Gabrys1 16 hours ago | parent | prev [-] | | Isn't X11 a protocol (and version 11 at that)? Being a protocol doesn't mean it can't be actively developed (look at HTTP at least), but if it's good it doesn't NEED to | | |
| ▲ | yjftsjthsd-h 14 hours ago | parent [-] | | Yes, X11 is a protocol, which is still slowly developed by adding extensions to it. Whether it does or doesn't need to be actively developed is a question of what features you do or don't think it needs. |
|
|
|
| |
| ▲ | silon42 a day ago | parent | prev | next [-] | | It's a blocker for Wayland migration for some of us. Maybe SteppeWM will be an alternative unless IceWM gets a Wayland compositor. | | | |
| ▲ | doublerabbit a day ago | parent | prev [-] | | Nothing wrong with legacy. |
|