[-] leopold@lemmy.kde.social 22 points 1 month ago

FIFO and commit timing are big for gaming. IIRC the lack of those protocols was a big reason why devs didn't want to enable Wayland support for SDL3 at first.

[-] leopold@lemmy.kde.social 19 points 2 months ago* (last edited 2 months ago)

Do you... not know how multi-licensing works? You can use the project's code under the terms of whichever license you prefer, you don't use all three at once. Simply putting the AGPLv3 does remove unfair restrictions, because it means you don't have to use either of the proprietary licenses the project was previously only available under.

[-] leopold@lemmy.kde.social 18 points 4 months ago* (last edited 4 months ago)

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.

[-] leopold@lemmy.kde.social 21 points 4 months ago

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

[-] leopold@lemmy.kde.social 23 points 6 months ago* (last edited 6 months ago)

Wine doesn't wait for major versions to merge major features. Major versions like Wine 9.0 are considered stable and are preceded by a feature freeze and multiple release candidates. Minor versions like Wine 9.9 are not, they're just released every two weeks from the master branch. This means nearly all of Wine 9.0's killer features were already present in the final Wine 8.21 minor version. The same will be true with Wine 10. Wayland support will continue to improve incrementally in the coming versions.

[-] leopold@lemmy.kde.social 19 points 6 months ago

it's a frontend for ollama. so no, because under the hood it is ollama.

[-] leopold@lemmy.kde.social 20 points 6 months ago* (last edited 6 months ago)

VP9 is AV1's predecessor and VP8 is VP9's predecessor. Dunno what the “264K 360° Surround sound 3D VR” thing is about, but AV1 is a good general purpose video codec and I recommend using it, with Opus audio.

EDIT: I should add, h264 and h265 are non-free because of software patents, for which there are licensing fees. There are free implementations and there always have been, but the extent to which these implementations can actually freely be used legally is limited by this. Cisco's OpenH264 is an exception, because there is a cap to the licensing fee and Cisco is already paying the max amount. This allows them to freely distribute binaries for their h264 implementation without having to pay additional licensing fees for every user. It's a clever loophole, but there are still limitations, namely that you have to be using Cisco's pre-built binaries. If you want to use the source code, you still need to pay for the licensing fee.

Because patents last twenty years and the initial release of h264 was made in August 2004, the key h264 patents should all expire within the next few years, which will eliminate the problem. h265 however was introduced in 2013 and its patents still have a good decade left in them.

[-] leopold@lemmy.kde.social 17 points 7 months ago* (last edited 7 months ago)

Or Blender? Or Cinelerra? Or ShotCut? Or OpenShot? Or Olive? Or Pitivi? The open source video editing landscape is frustrating. So many competent projects competing with each other, none of which have clear superiority. And nothing that comes close to the proprietary offerings. Feels like we might be closer if developers weren't split eight-ways.

[-] leopold@lemmy.kde.social 17 points 8 months ago

Faster to the fight for what? Wayland? Xfce doesn't even have a working Wayland session yet, so surely not. The new Plasma update is indeed being hyped for stability and Wayland. Wayland is finally ready to be used by default and that's a big deal. Many of the biggest issues with 5.27 have been fixed, which has improved usability a lot. HDR is also a big deal, people have been waiting for years for it to work on desktop Linux. Yes, there is also a lot of "eyecandy". People constantly complain Plasma looks ancient compared to GNOME, so they're doing something about it.

[-] leopold@lemmy.kde.social 23 points 8 months ago

Linux needed a universal package manager and it got three. Snap is not needed.

[-] leopold@lemmy.kde.social 18 points 9 months ago* (last edited 9 months ago)

Activities do a lot more. Virtual desktops are purely a window management feature. They contain windows and very little else. Activities can have different, panels, wallpapers, desktop icons, etc.

42
47
29
36
27
69
9
Ruqola 2.1 Beta (jriddell.org)
41
44
31
Season Of KDE 2024 Projects (mentorship.kde.org)
submitted 10 months ago* (last edited 10 months ago) by leopold@lemmy.kde.social to c/kde@lemmy.kde.social

None of the GitLab projects in the post seem to work, for some reason. Maybe they forgot to make the issues public.

EDIT: It's fixed now.

29
32
[-] leopold@lemmy.kde.social 20 points 10 months ago

I mean, not really. You own the stuff you create regardless of who's hosting it. Microsoft doesn't own the copyright for the millions of projects hosted on GitHub either.

view more: ‹ prev next ›

leopold

joined 11 months ago