LXQt – The next generation of the Lightweight Desktop Environment
lxqt.org
lxqt.org
I'd bet the majority of the lightweight "Windows 95 clone" WMs and DEs exist because GNOME and (to a lesser extent) KDE alienated their userbases by trying to be "different" and "next generation" (mostly by poorly cloning OSX and the latest Windows version that nobody liked anyway), so I'd hesitate to say that experimentation should be left to them.
EDIT: Many commercial products suffer from this problem where the existing version is "good enough" and people are happy using it for several hours a day, but the producer needs to convince users to purchase the new version anyway, so they end up adding a lot of pointless, irritating, and even product-breaking changes just to make the new version seem revolutionary and worthy of an upgrade, even if it's actually making the product worse. Many open source devs don't seem to have realized that there is no reason for them to play this game. They don't need to sell anyone a new version in a cardboard box, so there's no conflict of interest here; they can do less work and make their users more happy by keeping things stable and incrementally improving things. Yet, very often, they ape Microsoft, Adobe, and company's spastic thrashing anyway. More ribbons!
In fact, I would go so far as to say that the only time when a massive change to the desktop environment is warranted is when there's a massive change to the physical method that people use to interact with computers. The widespread availability of the mouse gave rise to the now-familiar WIMP paradigm. The introduction of multi-touch triggered another round of innovation, but I doubt that this can be backported to keyboard-and-mouse devices any more than Photoshop can be backported to mouseless terminals.
Sometimes change is good. Just because we do something one particular way (in the world of desktop environments this is often down to a decision made in the early 90s) doesn't mean that it's the most productive method of doing it. Often initially unpopular changes in user interface prove to be more effective.
The problem is that change for changes sake is different to change for UI improvements sake, but the two are often hard to distinguish between. How do we know that a new UI implementation is better or worse than the old one? You don't really until it's being used in the real world. There's not an easy answer, but I don't think that grinding innovation to a halt is the right one. I guess the beauty of the open source world is that there's room for a minimal non-progressive UI as well as a number of innovative ones.
So the menu bar wins now, but principally because its learned (the hard way). Now it would be even harder to switch to anything else.
While it's obvious that MS would have a reason, I have no clue what that could be. The only thing I can think of is that people seem to use Google rather than their app's help functionality even if the latter would do a better job.
The Office team, however, seems to operate more or less independently from the Windows team. The ribbon, for example, was first unveiled around the time Windows Vista was released, but Vista had no ribbon anywhere. Windows 7 added the ribbon to a few random apps, like MS Paint. Windows 8 added it to a few more random apps, like File Explorer. But they don't seem to be in any hurry to unify the look and feel of their own flagship products.
Well, what else could we expect from a company that thinks it's OK to slap two completely different UIs (Metro and desktop) on the same OS? Microsoft UI is schizophrenic.
If I want an environment for my desktop, I'll use an environment designed for a desktop; like Windows 95 - 7, Gnome2, KDE3, Xfce and LXDE.
My desktop has a keyboard and a mouse, not a touchscreen. In fact, I really don't want to be touching my $1200 ZR30w monitor anyway, even if it were touch-enabled. Cell phone OSes on the desktop work about as well as desktop OSes do on cell phones. Play to strengths, do not reduce to the lowest common denominator.
If an idea objectively improves productivity, I will give it a fair chance. And we have certainly seen that since Windows 95: most notably with tabbed interfaces. But I can't stand change for the sake of change. Just because an idea is old does not mean it is bad.
LXQt seems like it could become what KDE should have been. All they really need is to also merge with the Trinity people.
http://sourceforge.net/p/cdesktopenv/wiki/Home/
It's not all about resources. I don't want animations for every action. For me simplicity is elegance.
I installed FreeBSD at home and attempted to emulate the setup, but never got it quite right.
If you care about UX innovation, LXDE is not for you. That niche is filled by KDE 4, Gnome 3, and Unity. With XP support ending, I've used LXDE (Lubuntu) to rescue 2 old family machines that Gnome 3 and KDE couldn't handle without thrashing.
How does the memory usage of LXQt Desktop compare to LXDE and Razor-qt? I hope they've managed to keep it down.
fluxbox - active and kind've interesting
awesome - more of just a WM than full DE
ratpoison - ditto
enlightenment - okay, kind've resembles Win 95 too... but more of a DE than the others you listed
windowmaker - been around forever; hasn't really "innovated" in forever; just a NeXT clone if I remember correctly for GNUStep
I think my point stands. I was talking about LXDE, Xfce, and RazorQT.
>enlightenment - okay, kind've resembles Win 95 too... but more of a DE than the others you listed
> etoileos - last news update 2012 and wasn't even about the project
What you seem to be missing is that these projects died because people thought they were weird, which is to say, innovation in the DE space pays negative rent, and that's no good, especially not from the perspective of an open-source project, which, the social dynamics of open-source dictate that projects need to acquire a large userbase to sustain an active development community for more than a couple years, that is to say, to make people keep working on it after the "new project smell" wears off.
In other words your observation is a direct consequence of the choices in DE that users have made and continue to make.
The recent trend has been towards modularity, and while you dismiss awesome and ratpoison, a major boon of LXDE et al is that, unlike Windows 95, you can replace the window manager with xmonad and still use all of the other components of LXDE. Modularity brings innovation to the people who want it while satisfying the large majority of users who apparently do not.
There's no reason for LXDE to ship anything but Openbox; LXDE could certainly switch to xmonad tomorrow, but their users wouldn't be happy. And who wants that?
Actually, at least two of those (E and WindowMaker) remain alive. And WindowMaker's got its fervent fans (you're hearing from one here).
While Raster's continued to plink away at Enlightenment, among the reasons WindowMaker development's been so modest is that it accomplished its mission: provide an implementation of the NexTstep interface. I use wmaker without most of the rest of the GNUstep tools (I find them kind of funky and cumbersome), but the window manager itself is simple, straightforward, and rocks.
It's also very similar under the hood to Aqua as used now in OS X, which for the most part just skins it differently and removes a bunch of features I like -- so while I love wmaker, I really can't function on Macs.
As for userbase. Yeah. I'm aware that I'm in the minority. I'm totally OK with that.
BTW, putting off window manager/desktop environment philosophy arguments, Input Method Engine is one of those constantly neglected aspects that really matter for East Asian users. It seems that the ones making plans for WM/DE and other infrastructure had little overlap with users, and their designing decisions were very likely to omit the requirements necessary to cooperate with IMEs.
I'm not enough of a dev to know what would be required, but pitching this to the developer(s) might be helpful.
The only thing that's not happening is a whole lot of development. And I'm actually totally OK with that.
dat Typo. "étiolé"= withered in French.
I'm using it now... I think my search is over :)
Thank you!
Also see this comparison of tiling WMs: https://wiki.archlinux.org/index.php/Comparison_of_Tiling_Wi...
Update: I lied. i3 looked too good to wait for so I tried it, and it feels a lot more natural. I'm quite certain this will be it!
Bonus: If you're an Emacs user the interface/keyboard shortcuts should make you feel at home (or so I've heard).
Before that, I used XFCE. I have realized there is always another level of minimalism down from where you were before in Linux, until you hit the Linux console. But I love StumpWM. They might say it is not minimalist, but it is for me and it rocks my world.
I am going to hit submit and then hit a shortcut to open running term emulator and find my running mutt instance in tmux. Later full DE users.
I've set a reminder to switch to StumpWM 2 days from now.
Emacs is something I've never tried though Lisp is amazing and that's reason enough to use it.
So many fun toys, so little time...
IMHO I've used buggy software that happens to be written in Vala, but I wouldn't say it is because of the language.
But this is partnof their strength - one thing done well, and allowig the user to add everything else they want.
Mate is excellent and truly deserving of the title "modern Gnome2". It's my desktop of choice. Under the hood it's using a lot of Gnome3 tech while the user interface is familiar and usable for desktop users. The problem remains, however, that it is stuck with either a languishing GTK2 or at the mercy of Gnome with GTK3.
Perhaps you'd like to explain further?
The window list extension doesn't allow you to change the order of windows with drag and drop and I'm not sure if its possible at all. You also have limited options when you right click on them.
The workspace switcher as part of the window list extension or the stand alone extension are now text only menus that require multiple clicks to change desktop.
You cannot drag and drop launchers from the application menu anymore, in fact you can't have launchers on your panel at all anymore.
The system monitor applet is not visible on your panel anymore.
gnome-control-center is extremely limited, you must also learn to use gnome-tweak-tool and dconf-editor.
Also, classic mode just looks ugly and there is probably no way to change it without getting your hands really dirty.
Many of the things listed above used to work in classic mode but the functionality was removed in newer releases. There seems to be a trend of removing functionality from the desktop and moving it all to the activities overview.
Problem 2: you want a VM with a DE but don't want to spend too much resources in it.
Problem 3: you have a modern computer but prefer to have a lightweight DE and let the rest of the resources be used by your applications.
Both LXDE and Razor-qt consumed about 100MB of RAM, I would expect something similar from LXQt. All the other DEs are heavier, XFCE is just a bit heavier but at least for me LXQt looks a lot nicer.
And as it was pointed out, it's a merger of LXDE and Razor-qt, so it's the complete opposite of the "many Gnomes" situation. Kudos to that.
I'll certainly build a VM with it to try it out, but my concern is that unless it gets some sort of traction it will just sort of fizzle out as folks graduate and move on to other jobs.
I've been using Mate (on Mint) happily, but I'll definitely give this a try on one of my laptops.
Deleted comment
As for why the switch the Qt, I'm guessing it's because the next version of Unity/Ubuntu will be Qt based so this will be more compatible with that.
And Qt seems like is here to stay. So probably not bad decision from technical point of view too. It was nice when I used it.
LXDE on the other hand was specifically crafted for low-end systems. It's homepage says that it has been tested on PentiumII/266 with 192MB of RAM among others.
LXQt is the new merger of the two projects.
Personally, I'm glad to be done with overlapping windows and graphical file browsers. I use Xmonad, urxvt and bash.
If LXDE wouldn't exist, I would just use XFCE.
it seems very similar to LXQt and the project it replaces when it comes to resource usage and useability, except it is more mature and support a few more things.
Thats basically what keeps me on KDE. I would think KDE should disable akonadi and stuff by default personally - its super useable without all the heavy weight "crap".
Alt-F2, konsole and kwin basically are the reasons I use it.
Here's an example, too: I can tile my windows on any desktop i want with kwin without sacrificing non-tiling windows. I can even mix tiling and non-tiling. I dont have to remember 20 shortcuts for this, it works with the mouse too. Basically, its seamless.
(Thats also why I use it over awesomewm for example)
I agree. Unfortunately, they replaced Nepomuk with Baloo in 4.13 (I think; Baloo seems more aggressive than the former) and have effectively taken the stance that users cannot (easily) disable it [1]. It's somewhat infuriating, because adding your home to the ignore list doesn't appear to work as advertised and it'll happily index everything including /var (bug?), NFS mounts, and anything it gets its grubby mitts on. The only solution I found that works is here [2] because there's no longer a UI to disable it (unlike Nepomuk). Beyond that, you're absolutely right: With all the cruft disabled, KDE is quite nice (long time user here as well).
That said, I'm happy with KDE, and I enjoy it in part because of the eye candy (probably a poor excuse). I've used LXDE on an old laptop before but there are always features that I seem to miss. Otherwise, it's great for users looking to avoid the cruft or have limited resources. LXQt brings some of the clean appearance of modern KDE with it, so that's a definite plus. It makes me eager to take it a spin, then possibly try it out on that old laptop--which doesn't play nicely with KDE no matter what's disabled.
[1] http://vhanda.in/blog/2014/04/desktop-search-configuration/
[2] https://bbs.archlinux.org/viewtopic.php?pid=1390267#p1390267
"There is no explicit “Enable/Disable” button any more. We would like to promote the use of searching and feel that Baloo should never get in the users way. However, we are smart about it and IF you add your HOME directory to the list of “excluded folders”, Baloo will switch itself off since it no longer has anything to index."
This philosophy is why I stopped using GNOME and now prefer Xfce. I'm looking forward to trying LXQt when it's more stable.
EDIT: looks like 4.13.1 will also have a check box to disable Baloo! https://projects.kde.org/projects/kde/kdelibs/baloo/reposito... which is great news.
FINALLY. Thanks for digging this up. Having no means of presently disabling it through the UI seems unnecessarily user-hostile.
> Baloo had decided that it would index all of my data files which are huge (multiple GB) which was going poorly for it and for me.
As I mentioned in my previous comment, Baloo seemed to happily go about its business indexing precisely everything I told it not to, even to the extent of ignoring child directories of those I specified in the ignored directory list. I suspect that was a bug, but considering the suggestion in lieu of a button to disable the feature was "just add your home directory and it'll do the right thing" (which didn't work) is counter productive.
Sigh.
I can understand being excited about a new feature and (possibly) being one of its only proponents, and occasionally something good surfaces from such thankless chores. But I sometimes have to wonder what the motivation is to staunchly defend decisions that seem rather... myopic. Ordinarily I wouldn't care, but pounding the heck out of partitions and NFS mounts to do something that I can do quickly and simply with grep and find is just insanity.
On the other hand, now I understand why xapian-core is listed as a dependency.
The first principle of GUIs is that there's been very little real innovation since the first demos at Xerox PARC at the Mother of All Demos 46 years ago (https://en.wikipedia.org/wiki/The_Mother_of_All_Demos).
And there's been little reason for it. Once people understand how to interact with the basics of their interface, there's little gain, and a lot of cost, to changing things.
Most computer interaction is textual. Some isn't. Supporting text, formatted text, images, video, and sound is pretty much the entire scope of what needs to be done.
The best interfaces haven't changed much. Apple's Aqua interface is hardly changed from its introduction in 2000 -- that's 14 years. Some visual elements have been modestly restyled, and virtual desktop support added. That's pretty much it.
Other attempts to push radical UI changes on users have been dramatic failures, whether from Microsoft or Linux. Windows 7 was an absolute flop, and I'm among those who've been massively disappointed and frustrated by the GNOME 3 and KDE 4 transitions. While neither is my primary desktop, I do interact with them occasionally, and with apps designed for them more frequently. The experiences have been disappointing and frustrating, to say the least, as well as the attitude shown toward users by the development teams (Linus Torvald's outburst to GNOME was pretty much on point).
The place to experiment, IMO, is precisely where LXQT is: in an experimental space, away from the mainstream. If the desktop does prove useful, people will tend to migrate toward it, as has happened with the xfce desktop: not as featureful as GNOME or KDE, but vastly less frustrating and more useful (I also try it from time to time).
My own home? WindowMaker, which I've used for 17 years. I know it, it knows me, we work well together, and I see no reason to change.
I'm currently using Lubuntu which is Ubuntu+LXDE but then with Xmonad as a window manager and really enjoying it.
It totally does: fast, stable, restartable (kill -USR1 <pid>), lightweight, stays out of the way, easily configurable, portable config files, and a very, very, very consistent UI over the past 17 years that I've been using it (nearly a decade of which it saw virtually no dev activity and, frankly, didn't need it -- updates have started trickling in again).
Thing is, after nearly two decades, it's solidly ingrained into my desktop use habits. And while I try alternatives from time to time, they always leave me running screaming back to good old wmaker.
The reason for this is that there are relatively few graphics artists who use Linux desktops and contribute to the desktop projects by creating graphics.
But there are quite pretty custom desktop themes created by people. You can look at /r/unixporn for example. Most of the screenshots there are from the tiling wm (dwm/awesome/xmonad/i3) crowd but every now and then someone posts some pretty Gnome/KDE/LXDE/Xfce screenies and themes as well.
I just showed a MacOSx user the alt-drag window resizing.... totally blew his mind, as in he couldn't understand why that wasn't a feature of MacOSx: "The Simple Operating System"
I do think the default LXDE theme looks rather windows 2000/Gnome 2.6. However, changing the theme is not hard and LXDE can use any XFCE themes. Hopefully the new LXQt preserves that compatibility.
Does anyone know of a window manager that can group windows so that they raise together? Or perhaps something more like: 'when I raise this window also raise these windows.'
Obviously you need a bit more logic to deal with the ordering of windows within a raise group, but this seems like a feature that is completely missing from all current window managers.
It's a rather complicated approach, but I've never found any better multi-tool layout, since it's enormously Fitt's-law-friendly while allowing me to both hide everything or bring in oodles of tool panes quickly and easily as needed.
I suspect it could be extended to use this to start setting up tiles automatically.
I wonder how this LXQt might compare to Maynard [2] resource usage.
[1] http://youtu.be/0j-Wakm5B84 [2] http://www.raspberrypi.org/preview-the-upcoming-maynard-desk...
You might find some useful info regarding Crunchbang/LXDE here http://crunchbang.org/forums/viewtopic.php?id=24640
Part of the appeal for me as an artist and hacker, the Crunchbang community is incredibly creative. You can see the personality and careful attention going into the screenshots. Any pixel on the screen is fair game for customization. In my opinion, it's worth the effort to tweak your config files and get exactly the look you want. For me it's a balance between functionality, getting the most from my laptop's small screen, while creating a pleasant work environment that I don't despise.
FWIW I still use Openbox but disabled the decorations. I use pytyle2 to manage windows. Pretty much I use the Crunchbang default colors, dark but not too dark, works well at night as well as in daylight.
The windows actually look really nice, especially considering it's the default skin.
When you let a programmer dictate the design, you end up with a lot of features and a lot of misaligned margins. In my experience, many programmers just don't care about pixel-perfect designs. Yes, I'm talking about the same group of people who scoff at typography because "the content is the only thing that matters", blah blah blah. Admittedly, I have no data to back this up, but I have a gut feeling that lightweight desktop environments are particularly teeming with this "function before form" crowd. When you treat design as a second-class citizen of your project, it's no wonder you can't attract good designers to work with you.
On the other hand, when you let a designer dictate the design, you end up with perfectly aligned margins and anti-aliased corners, but all the features and configuration options you care about are hidden behind five clicks and a keyboard shortcut, or worse, removed entirely because they somehow violate the designer's philosophy :(
Just doesn't feel nice.
But those I have played with, KDE, XFCE etc. (disclaimer.. I haven't tried this one) are generally very tunable and can look quite nice when customized.
I agree with poster who mentions the panel though. Usually they aren't so good. Although with a semi-transparent panel my KDE desktop looks pretty good to me at least.
> To be honest, migrating to Qt will cause mild elevation of memory usage compared to the old Gtk+ 2 version. Don’t jump to the conclusion too soon. Migrating to gtk+ 3 also causes similar increase of resource usage.
1) QT works better when you not have accelerated drives (ie SVGA driver in X11)
2) The time in Nokia, QT was optimized to run in a mobile !! So must they tuned it to be more lightweight.