4 ms·
> AFAIK, the only Linux desktop environments that come close are GNOME and Unity. I'm the project lead of LXQt. All those things you listed can be supported wi
by scrollaway 11y ago
> AFAIK, the only Linux desktop environments that come close are GNOME and Unity.
I'm the project lead of LXQt. All those things you listed can be supported without introducing much bloat at all. In DEs, most bloat comes from pure technical debt. Unnecessary libraries, duplicated code/libs, etc.
Feature bloat is another matter and is more subjective. A lot of it is down to UX.
Fun fact: KDE 4.x depends on ruby in most distros. Do you know why? Dolphin ships with a ruby script to update some folders (don't remember what it does). Nobody runs it. That's it.
- Twirrim 11y ago> Fun fact: KDE 4.x depends on ruby in most distros. Do you know why? Dolphin ships with a ruby script to update some folders (don't remember what it does). Nobody runs it. That's it. Why did they allow an additional dependency on Ruby in? It seems like perl or python would be the more logical choice, given they'd already be on the system (heck.. maybe bash?)
- exprL 11y agoProbably because a Ruby activist wrote a cool script and no-one cared about the implications of a new dependency at all.
- digi_owl 11y agoI fear many projects seems to take the infrastructure and manpower of large distros for granted these days.
- scrollaway 11y agoBash would have been more appropriate, yes. I don't think the author of the script even thought it was going to be run by users, but some debian package checker probably flagged ruby as a dependency and there it was.
- tikums 11y ago> Bash would have been more appropriate A script that is compatible with POSIX Bourne shell (/bin/sh) would be more appropriate. FreeBSD, for example, does not come pre-installed with bash. If you want cross-platform portability, this is a better default.
- johnny22 11y agodon't forget about backwards compatibility.