73
[-] leopold@lemmy.kde.social 41 points 1 month ago* (last edited 1 month ago)

The article you linked makes a big deal about literally nothing. We've known Chrome was going to drop MV2 for years. We also know Firefox won't. There is nothing more they have to do or say about this situation. It doesn't affect Firefox whatsoever.

"Suspiciously silent" is such a bullshit nothing accusation to make. It is so obviously trying to capitalize on how many users have been (justifiably) turning on Mozilla as of late.

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

Kinda insane how many people in a nominally open source community are defending this guy for switching to a proprietary license. If DuckStation gets shut down then I say good riddance. It is not the only PS1 emulator in town and I will not miss the endless flow of Stenzek-related drama.

30
[-] leopold@lemmy.kde.social 33 points 2 months ago

Er, yes. It's one of the main features being introduced in 3.0. I don't know why you would just assume they're not adding it without looking it up. It made quite a bit of noise when it started being in the works.

[-] leopold@lemmy.kde.social 34 points 2 months ago

Basically everywhere I go on Lemmy you're there spouting ignorant bullshit, garbage takes, rage-bait and misinformation. You're inescapable. This is the perfect example. You know what you're saying is wrong. You know you're being dishonest. Do you wanna know how I know? Because I literally told you as much less than two weeks ago when you tried spreading the same lies. But you didn't care back then and you still don't care now. The only thing you seem to care about going by the other things I've seen you post is pushing your favorite projects, and you will use all of the arguments available to do so, including the ones that you just entirely made up. You think LadyBird is the better project and are trying to spread the belief that Servo is dead to make others buy into the LadyBird hype further. But, of course, Servo verifiably isn't dead and in fact the Servo team writes up monthly blog posts detailing their progress, which show the project developing at a healthy pace. And to top it all off, when these facts are pointed out to you, your only comeback is "means nothing". Clearly you're not the kind of person to let facts tie you down.

[-] leopold@lemmy.kde.social 33 points 2 months ago

Because it doesn't matter for most apps. XWayland works fine.

Even Blender says if it fails to use Wayland it will use X11.

What are you trying to say? Of course it does. Pretty much every Linux app still supports X11, because a lot of people are still using X11. Only exception I'm aware of is Waydroid.

27
KStars 3.7.2 Released (knro.blogspot.com)
20
[-] leopold@lemmy.kde.social 115 points 3 months ago* (last edited 3 months ago)

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.

20
Kate and OrgMode (akselmo.dev)
[-] leopold@lemmy.kde.social 44 points 4 months ago* (last edited 4 months ago)

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.

29
Release of KDE Stopmotion 0.8.7 (gruenich.blogspot.com)
[-] leopold@lemmy.kde.social 34 points 5 months ago* (last edited 5 months ago)

It's not an unpopular opinion that Apple is the only one that does sleep right. It is an unpopular opinion that this is only possible because they have a complete walled garden and that open platforms are fucked, especially considering it is easy and common to install applications from outside the App Store on macOS. We used to have sleep figured out, that's what S3 was. But then hardware vendors dropped it. So yes, drivers and hardware vendors are part of the problem. The Steam Deck is an example of an open platform where sleep works fine.

13
[-] leopold@lemmy.kde.social 39 points 5 months ago* (last edited 5 months ago)

Sure.

Wine 9.9 bug fixes:

#56000 Window title is not set with winewayland

Wine 9.8 minor changes:

winewayland.drv: Enable wglDescribePixelFormat through p_get_pixel_formats.
winewayland.drv: Set wayland app-id from the process name.
winewayland.drv: Implement SetWindowText.
winewayland: Get rid of the now unnecessary surface wrapper.

Wine 9.7 minor changes:

winewayland: Remove now unnecessary swapchain extents checks.
winewayland: Remove now unnecessary swapchain wrapper.

Wine 9.5 minor changes:

configure: Check the correct variable for the Wayland EGL library.
winewayland.drv: Implement wglCreateContextAttribsARB.
winewayland.drv: Implement wglShareLists.
winewayland.drv: Implement wgl(Get)SwapIntervalEXT.

Wine 9.4 major changes:

Initial OpenGL support in the Wayland driver.

Wine 9.4 minor changes:

winewayland.drv: Add skeleton OpenGL driver.
winewayland.drv: Initialize core GL functions.
winewayland.drv: Implement wglGetExtensionsString{ARB,EXT}.
winewayland.drv: Implement wglGetProcAddress.
winewayland.drv: Implement wglDescribePixelFormat.
winewayland.drv: Implement wglSetPixelFormat(WINE).
winewayland.drv: Implement OpenGL context creation.
winewayland.drv: Implement wglMakeCurrent and wglMakeContextCurrentARB.
winewayland.drv: Implement wglSwapBuffers.
winewayland.drv: Handle resizing of OpenGL content.
winewayland: Remove now unnecessary vulkan function name mapping.
winewayland: Remove unnecessary vkDestroySurfaceKHR NULL checks.

New minor versions of Wine are released every two weeks. Last major Wayland update was in 9.4. Smaller updates have happened every release since, except 9.6.

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

nearly your entire system is written in C and you're worried about a simple fetch program

26
39
103
submitted 7 months ago* (last edited 7 months ago) by leopold@lemmy.kde.social to c/kde@lemmy.kde.social

Amarok was KDE's flagship music player during the KDE3 and Plasma 4 days. For Plasma 5, a new music player called Elisa was created with Kirigami which is the current KDE flagship music player. The last full release of Amarok was 2.9.0 in 2018, still targeting Qt4. A Plasma 5 port was started with the intention of being released as Amarok 3.0, but despite a usable alpha 2.9.71 release in 2021, the full 3.0 release was never completed. Outside of the occasional odd pull request, the project was essentially dead and was listed as unmaintained by apps.kde.org.

Two weeks ago, occasional contributor Tuomas Nurmi, author of over a third of these pull requests, made a push to become an Amarok maintainer, starting this thread in the mailing list: https://mail.kde.org/pipermail/amarok-devel/2024-March/014748.html

In the thread, Tuomas expresses his desire to revive Amarok. He believes a second alpha for 3.0 can be released in mid-April and a full Plasma 6 port could be completed within 2024 after the release of 3.0. Tuomas has since created a fair amount of merges and fixes in preparation for 3.0 and has shown no sign of stopping.

This is very exciting news. For many, Elisa isn't a satisfying replacement for Amarok. It simply doesn't come close to matching Amarok's power and features. It also has the drawback of being a convergent application, meaning compromises have to be made to make the interface work well on smartphones.

It's also victim to the many drawbacks of Kirigami. Theming is worse since Plasma has to convert QtWidget themes to QtQuick themes, which works great for Breeze, but meh for everything else. There is no good equivalent for KStandardAction/QAction, KHamburgerMenu or KStandardShortcut. Any Kirigami app that wants customizable toolbars and shortcuts need to go out of their way to implement them, while QtWidgets apps just get them for free. You also don't have a good QDockWidget equivalent that I know of. Apps that do bother to reimplement some of these features (Haruna is the only one I know of) still don't have toolbar customization to nearly the same extent QtWidgets apps do. Most Kirigami apps don't bother with this at all and lose a lot of customizability in the process. Elisa is not Haruna, tho. There is no shortcut customization, there is no toolbar to customize and that hamburger menu can't be turned into a menubar.

For years, the solution was Strawberry, a fork of Amarok still under active development. Thing is, Strawberry is a fork of Clementine, itself a fork of Amarok 1.4. That's old. That's 2008 Amarok, not 2018 Amarok. Clementine had its first release in 2010, when Amarok was still going strong. It was for good reason, Amarok 2.0 introduced a very divisive redesign of the interface, which prompted a fork. But this means 2.0+ Amarok and Strawberry are actually very different beasts. For those who were using Amarok 2.9, switching to Strawberry meant switching to a new music player, making it far from an ideal successor. So I'm very much excited for the return of Amarok, the best music player KDE has had.

26
Haruna 1.0.2 (haruna.kde.org)
13
Kile 2.9.95 / 3.0 beta 4 released (gruenich.blogspot.com)
[-] leopold@lemmy.kde.social 49 points 9 months ago

Can people who very clearly haven't read the article stop commenting the equivalent of "works on my machine", please? I know it's a long article, but it's worth a read. It's not anti-Wayland and it's definitely not pro-X11. It just outlines a few limitations of Wayland and problems with how Wayland is currently being developed. It's a great follow up to Nate's blog post, which was posted here a while back and got pretty popular.

[-] leopold@lemmy.kde.social 37 points 10 months ago

Oh boy, 102 comments. Knowing Phoronix, I bet those are a treat to read.

view more: next ›

leopold

joined 11 months ago