leopold @ leopold @lemmy.kde.social

Posts

0

Comments

239

Joined

2 yr. ago

I'm pretty sure the video is just badly misnamed. PackageKit is an abstraction layer for interacting with native packages in a cross-distro manner. It's used by both Discover and Software Center. It is developed by Red Hat, but not as a part of GNOME.

Because of widespread fearmongering, itself caused by the filesystem taking too long to become stable and garnering a bad reputation as a result which it has never shaken off.

having support for the newer wayland protocols in the wayland session wouldn't hurt

it's definitely progressed a lot since 2008, but the last couple of years have been extremely slow

FDO stands for FreeDesktop.Org, the committee responsible for various desktop Linux standards including icon themes. So FDO icons just refers to your system icon theme, which LibreOffice doesn't use.

LibreOffice uses its own widget toolkit. It works similarly to wxWidgets, basically just maps to whatever toolkit is native on the current platform. It uses Win32 on Windows, Cocoa on macOS, Qt on KDE, GTK on GNOME and a few others.

That said, their current approach to dark themes is pretty bad. It can very easily conflict with the dark theme from the host toolkit and cause issues if misconfigured, which has caused a lot of people to think it just doesn't work. It does work, but it can be confusing as hell to configure correctly.

For instance, LibreOffice has a setting you can use to change the application colors. It barely works and you should never touch it. Just let it get the colors from your toolkit.

There's also the fact that LibreOffice doesn't use FDO icons and has its own icon setting which doesn't automatically follow dark/light theme. If you're using a dark theme, you have to manually switch the icon set to one that isn't impossible to see on a dark background.

Oh and if you want your documents to use a dark palette that's also a separate setting. Like I said, confusing.

It used to be open source, but large parts of it have been relicensed under their proprietary source-available shared source license. The reason why it isn't entirely proprietary is that it's based on Firefox, which is entirely licensed under the MPL. The weak copyleft of the MPL states that all parts lifted from Firefox must remain open source, but the new parts can be proprietary.

Source-available licenses are a type of proprietary license where the code is made public for people to look at, but you're not actually allowed to use it. Users can still contribute upstream, so they're usually parasitic licenses aimed at getting free labour out of the userbase without actually giving back any code to the commons, all while keeping up the illusion of being open source. It sucks.

The job of the window manager is to manage windows and very little else. Font rendering is done by the widget toolkit, usually via freetype/harfbuzz.

I set up mine same as I did on desktop. Copied my custom filters over and enabled all of the default ones. Works well enough.

Because it's not actually a good idea.

You create text that is basically impossible to search. Like, for instance, do a Ctrl+F on this page and search for "Bold". You'll see the example from OP doesn't get picked up, because it's not a B, it's a 𝗕. And it's not an o, it's an 𝗼. And so on. Or how about this? Go on Google and copy-paste this word from OP: "s̵t̵r̵o̵k̵e̵". Now, stroke isn't a particularly unusual word, but this thread is just about the only result Google returns. Because it's not stroke. It's s̵t̵r̵o̵k̵e̵.

It's also bad for accessibility. A lot of the time screen readers just won't know what to do with your bold or italic Unicode text.

And of course this only works for characters for which Unicode actually has these variants. Not a problem with the Latin alphabet, but what about Arabic? Cyrillic? Chinese? Devanagari? Hangul? Not gonna work.

These characters are from the Mathematical Alphanumeric Symbols code block. They're stylized Greek and Latin letters meant chiefly for use in mathematical contexts. The Unicode standard explicitly advises against using them to fake markup for the reasons outlined above and more. A simple markup language is just about always going to be preferable to faking it with Unicode.

Huh? How did you narrow it down to just GIMP? Are you excluding all non-GUI software or something? GUI has never been a big focus for GNU (which I assume is what you're referring to when you say FSF), though they do have a couple of projects like GIMP and GNUCash. Most notably as far as GUI is concerned, they instigated the GNOME project, though they later split off. But yeah, they still maintain extremely important tools, especially for developers and UNIX systems, such as glibc, coreutils, gcc, emacs, gdb, make, bash, grub, octave, guix, etc.

Source? Last I checked, the Steam Deck was very much in the minority even when narrowed down to just desktop Linux.

Yeah. xwayland isn't gonna die ever probably, so there's no rush.

At the moment, we have Blink (Chrome), Gecko (Firefox), Webkit (Safari), Servo, Ladybird and Goanna (Pale Moon).

At best, another Pale Moon is what would happen. They've been maintaining their own hard fork of Gecko by themselves since 2016. They clearly have people capable of maintaining a browser engine, though perhaps not quite enough of them. If Firefox were to die, perhaps joining up with Goanna would be the smart move.

There are significantly fewer Firefox-based browsers than there are Chromium-based ones, unfortunately. Out of the ones we do have:

Floorp has much like Vivaldi gone the proprietary source-available route, so you couldn't pay me to use it.

Pale Moon is easily the most involved of the Firefox forks, being a fork of a much older version of Firefox, but I wouldn't generally recommend it for security reasons. It does have its uses, though. Waterfox Classic is in a somewhat similar boat. Security-wise Pale Moon is definitely the better of the two because it uses its own fork of Gecko which is maintained about as well as you could reasonably expect given the manpower available to the project. Waterfox Classic meanwhile has kinda just been left to rot since most development is going to regular Waterfox nowadays, so it's not maintained nearly as well as Pale Moon and it's just been collecting CVEs. But for those same reasons if all you want is the ability to use legacy XUL extensions, then Waterfox Classic is gonna have better compatibility since it hasn't been modified nearly as heavily as Pale Moon.

LibreWolf is probably the most popular Firefox fork nowadays, but it isn't much more than a Firefox equivalent to Ungoogled Chromium. Waterfox goes a little further, but not by much. Both can be good choices, but personally I haven't had much reason to switch away from upstream Firefox. LibreWolf is tempting, but I can already disable pretty much all of the Firefox BS from about:config, so I don't see the point. It's pretty much just better defaults.

It is significantly less powerful when compared to LibreOffice, lacking support for many features. It offers less applications than LibreOffice. It is significantly less customizable than LibreOffice. It's built on bloated web tech. It lacks RTL support.

I am not paranoid about OnlyOffice's origin. I also do not think it is the best office suite on Linux by a mile.

FileZilla.

Is there any reason you need to switch other than the age of the last releases? Avidemux had its last release in 2022 and its last commit a week ago. For a piece of software with a fairly stable and unchanging set of features, that seems pretty reasonable to me. Avidemux still works fine on Linux and is still packaged by all of the large Linux distros, so I don't see the problem. VirtualDub's definitely dead, though.

IIRC the Krita people were working on redoing the text tool. Not sure if/when it's going to be finished, though.