News: 0001589343

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

LXQt 2.3 Released With Improved Wayland Support

([Desktop] 4 Hours Ago LXQt 2.3)


LXQt 2.3 is out today as the newest release of this lightwight, Qt-based desktop environment.

A major theme of LXQt 2.3 has been on continuing to enhance its Wayland support for those preferring to use Wayland over X11. The LXQt Panel has better Wayland support, desktop switcher support with more compositors, the custom command plug-in is now more flexible under Wayland, and screen grab functionality has started to work under Wayland.

The LXQt desktop switcher support works with Wayland compositors supporting the ext-workspaces-v1 protocol. LXQt 2.3 also adds advanced backend functionality when using with Wayfire. LXQt power management also now supports turning off the monitor now on Wayland with the KWin, Niri, or Hyperland compositors.

QTerminal meanwhile has added emoji flags support. LXQt Archiver has included LZ4 support for some of the non-Wayland LXQt 2.3 changes.

LXQt 2.3 downloads and more details on this new lightweight Qt desktop feature release via [1]GitHub .



[1] https://github.com/lxqt/lxqt/releases/tag/2.3.0


It is a very humbling experience to make a multimillion-dollar mistake, but
it is also very memorable. I vividly recall the night we decided how to
organize the actual writing of external specifications for OS/360. The
manager of architecture, the manager of control program implementation, and
I were threshing out the plan, schedule, and division of responsibilities.
The architecture manager had 10 good men. He asserted that they
could write the specifications and do it right. It would take ten months,
three more than the schedule allowed.
The control program manager had 150 men. He asserted that they
could prepare the specifications, with the architecture team coordinating;
it would be well-done and practical, and he could do it on schedule.
Furthermore, if the architecture team did it, his 150 men would sit twiddling
their thumbs for ten months.
To this the architecture manager responded that if I gave the control
program team the responsibility, the result would not in fact be on time,
but would also be three months late, and of much lower quality. I did, and
it was. He was right on both counts. Moreover, the lack of conceptual
integrity made the system far more costly to build and change, and I would
estimate that it added a year to debugging time.
-- Frederick Brooks Jr., "The Mythical Man Month"