leopold

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.

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.

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.

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

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.

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

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.

is this flamebait? we really don't need this stale-ass debate revived for the millionth time. everything that had to be said has been said and no one is going to budge from their positions. there is nothing to be gained from reposting some old controversial 2021 blog post about this outside of more flaming. it's time to move on. this is a waste of everyone's time.

if you're a developer, support themes if you want to support them, don't support them if you don't. if you're a user, use the apps you want to use. if you care about theming, use the apps that support it. if you don't, good for you. there doesn't need to be anything more to it.

It never occurred to me before reading this comment that there actually is a use case for the execute permission. To me it was always just this annoying thing I have to do whenever I download an executable which I didn't have to do on Windows.

So just to clarify, there's no way to support the DualShock 3 without introducing a security hole? Or is the security hole only a problem with the current driver which could eventually be fixed, rather than something inherent to the device? Also, is there a list of affected devices outside the DualShock 3? Will the Wiimote still work, for instance?

The DualShock is old, but I've always appreciated how I could have all of my gamepads just work on Linux, from the Wiimote to the DualSense. On Windows, most of them needed third party unofficial drivers to be installed and/or would be missing functionality, like motion controls or Bluetooth support. Would be a big shame if it just stopped working wirelessly. Still, I have a lot of significantly better gamepads by now, including a DualSense, so DualShock 3 support isn't something I really need anymore unless I have a lot of people over and need to connect a lot of controllers.

especially considering KDE already has an application with almost exactly the same name for the same purpose https://invent.kde.org/utilities/alpaka

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.

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

For what it's worth, glibc is very much performance-critical, so this shouldn't be a surprise. Any possible optimization is worth it.

There are a ton of free software libc implementations outside of glibc. I think most implementations of libc are free software at this point. There's Bionic, the BSD libcs, musl, the Haiku libc, the OpenSolaris/OpenIndiana libc, Newlib, relibc, the ToaruOS libc, the SerenityOS libc and a bunch more. Pretty sure Wine/ReactOS also have free implementations of the Windows libc.

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.

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.

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

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.

No. This is just a thing Discover does. Unless nearly every update I've done for every Flatpak I have installed on my Steam Deck have actually been downgrades.

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.

I would consider the "source code" for artwork to be the project file, with all of the layers intact and whatnot. The Photoshop PSD, the GIMP XCF or the Krita KRA. The "compiled" version would be the exported PNG/JPG.

You can license a compiled binary under CC BY if you want. That would allow users to freely decompile/disassemble it or to bundle the binary for their purposes, but it's different from releasing source code. It's closed source, but under a free license.

I mean, probably not. That's such a short post, chances are courts wouldn't find it copyrightable. And obviously attaching a license at the end of your comments is useless in practice, because no one on the internet actually properly engages with copyright law. Plus suing over copy-pasting someone's social media post is dumb as hell and no one does that, tho I do think you could technically do it and win, because current copyright laws make zero sense if you actually stop and think about it for any amount of time.

actual link https://xkcd.com/2347/

I believe what they meant is that Firefox Android is unable to open local HTML files, which indeed I have found to be quite annoying in the past.

It's even more bonkers than it sounds. If you look at the code locations for that KDE count, you'll see it also includes just about every KDE project. That's not just Plasma, that's hundreds of projects, including some really big ones like Krita, Kdenlive, Calligra, LabPlot, Kontact, Digikam and Plasma Mobile. Hell, it even includes KHTML/KJS, KDE's defunct web engine as well as the ancestor of WebKit and Blink. It even includes AngelFish and Falkon, KDE's current web browser frontends.

Same deal with GNOME. It includes just about everything on GNOME's GitLab, even things that are merely hosted there without strictly being GNOME projects, like GIMP and GTK.

And yet still they are both that far behind Chromium and Firefox. Modern web browsers are ludicrous.

why did it insert and translate some random japanese phrase in the lede

This has actually been the most positive reaction to a Firefox announcement I've seen in a long time. I've yet to find a piece of open source software users act more toxic towards than Firefox. It is impossible to find any Firefox-related announcement in recent years that's received broadly positive feedback. For a long time, the top voted comment would always be someone demanding tab groups or vertical tabs. Now they're adding those, which is probably why the reaction has been a bit more positive. But of course, AI and UI changes have become the new things to complain about.

It's C++ with Win32 API. Not portable. Very little incentive to do it considering advanced text editors that work on Linux are dime-a-dozen (Kate, VS Code, Notepadqq, Geany, Sublime Text, etc.)

try KvLibadwaita. otherwise, you can install gnome apps on plasma and use those instead of kde apps.

it is one of many non-GNOME GUIs

my experience with it is that it performs significantly better than the official Flash Player

It doesn't install any optional dependencies, is the problem the user seems to have.

Yes. It's a joke. It's pretty funny, IMO. I'm not sure how you could interpret it as anything else. The wording alone makes it pretty obvious.

There is no minimum market share threshold to discuss the way the software you use is being developed and PostmarketOS will not reach 4% in the foreseeable future (and it probably never will). Desktop Linux only just reached that threshold after decades of work and systemd arguments have been happening for years regardless. The conditions for mobile Linux are considerably less favorable. If we can't discuss systemd until 4% is reached, we can't discuss systemd ever. Which is fair, because the systemd horse has already been beaten to death at this point. But not because it hasn't reached some arbitrary 4% threshold. That makes no sense.

AppImages long predate Snaps, but yes, Snaps do predate Flatpaks by a few months. There's also Nix packages, which predate all three. Of course, this all matters very little compared to the merits of all four technologies. The heavy dependence on proprietary technology for repositories makes Snap clearly unsuitable to become the universal Linux package format.

No reason to use it outside of a Steam Deck IMO. Compared to other immutable distros, SteamOS makes things pretty difficult if the thing you're trying to run isn't on Steam, Flathub or AppImage. Can't just layer. Have to set up stuff like Nix yourself. Distro doesn't come with gcc/make/cmake, so good luck building from source if you ever need to. It's fine for a handheld PC, but as a power user I would never want it on my desktop. Not to mention the whole Gaming Mode/Big Picture GUI is just very limited and you have to constantly work around its limitations if you want to use it for anything other than Steam games.

I had an instance of SteamOS making things unnecessarily difficult yesterday. I wanted to use a Pokemon Ultra Sun/Ultra Moon HD texture pack for Citra. However, about a year ago there was a major rewrite of Citra's texture pack code which broke a few older texture packs, including that one. The author recommended using Nightly 1880 at the latest for the texture pack to work correctly. However, last month, the Github repository for Citra was taken down and all of the old prebuilt binaries went down with it. Many mirrors of the repository exist, but they at best only offer the last nightly for download. On any normal Linux distro, this would be a trivial problem to solve. Clone one of the many mirrors of the Citra repository, rollback to whichever commit corresponds to Nightly 1880 and compile. Can easily be done in ten minutes. But on SteamOS, you can't do that. What I had to do instead was going to the old Citra Github repository through archive.org and somehow finding an archived download for the latest Linux build of Citra released before 1880. This took a while, but I was eventually able to find a download for Nightly 1816, which I deemed close enough. Great. Except it didn't launch. Because it was linking to some shared objects SteamOS did not have.

So I had to go to the Debian website and download deb files for Debian Buster that included the so files Citra wanted. I unpacked the debs into the Citra directory and created a shell script that simply launched Citra with LD_LIBRARY_PATH pointing to the libraries I'd downloaded. I had to to get at least a dozen libraries from Debian before Citra finally stopped complaining about missing so files and successfully launched. Then I had to reconfigure this second Citra build to match my preferences and transfer my Ultra Sun save file to it. I also had to change my Steam library entry for Ultra Sun to point to the shell script. Oh and I obviously also had to install the texture pack. And then I finally had the texture pack working. After hours of work. When it would've taken twenty minutes at worst on any other distro. Yeah, in retrospect, fuck SteamOS.

RHEL is used and is meant to be used both for servers and professional workstations. I imagine clones like Rocky are much the same.

The idea that a web application for screen recording is less bloat than OBS is absurd. As this was the idea presented by OP, atzanteol reacted by figuratively saying that the word no longer had any meaning. Given the context, this was quite clearly not an attempt to downplay the effects or severity of software bloat, but simply a figurative use of the phrase meant to point out how badly the word bloat had been misused. You completely misinterpreted their comment. Then, when this was pointed out to you, you proceeded to do the Reddit thing of mockingly editing your original downvoted comment, successfully making an ass out of yourself.