Parsing the output of rm, cp, mv, and such tools seems volatile. Better to use their return codes, no?

For anyone testing the beta, the two lower-level changes are probably the ones most worth poking at before the 15 October release, since they're the ones most likely to break things silently rather than visibly:

• Rust coreutils is now complete, including cp, mv and rm. If you have backup scripts, deploy scripts or anything that parses the output of these tools or relies on less common GNU flags, run them on the beta now and report differences upstream to uutils. Behaviour differences in edge cases (symlinks, sparse files, odd permissions, error messages) are exactly what a beta is for.
• dbus-broker replacing dbus-daemon: mostly invisible, but if you have custom D-Bus policy files or services that do unusual things on the session bus, it's worth checking the journal for warnings after login.

The OOM change (core desktop processes getting lower OOM scores) sounds like a genuine quality-of-life fix for anyone who's had the whole session killed while a browser ate all the RAM.

This seems to have been fixed in 154, but it sounds like Brave hasn't updated yet

😂 Chrome 👏

For me it's mostly about the library. If it doesn't have the music I want to listen to, I have no reason to subscribe. I really, really wish Qobuz or Tidal had the library that Spotify does for my music taste. It's a shame, but the bitter reality for me.

I'm using it right now and they still haven't fixed the app not responding popup glitch whenever you load a game or program that takes more than 5 sec to launch like come on gnome just up the limit for the timer to 20sec or something.

I understand the hate for Apple but depending on where you live and how cheap you can get the subscription Apple Music (aside from Bandcamp of course) can be the one that pays out the most to the artists per stream. It's a per country, per market situation also in the Philippines Youtube Music pays close to what Apple pays per stream even though globally they pay the least.

Bunch of it used to be Novell once upon a time.

NDS > AD was a hell of a ride, even though it's all supposed to be x.500 (EEE)

AD > LDAP will be a pain point if they ever traverse that path, I suspect they won't though - MS Exchange is a hell of a drug.

You can make changes to the Firefox UI with CSS coding yourself: https://www.userchrome.org/ For example, my Firefox looks currently like this (looks pretty much the same in a non-private session too), just like my operating system with KDE:

It's a complex mix of addons, custom CSS, custom JavaScrip, some custom settings in Firefox and so on. You can copy CSS codes into your userChrome.css file, some good sources I use are:

• CSS for userChrome.css: https://github.com/MrOtherGuy/firefox-csshacks
• JavaScript for user.js and prefs.js: https://github.com/yokoffing/Betterfox

Installing Firefox does not fix the Chrome/Chromium issue, because KDE would crash on login regardless. I already use Firefox as my main browser since version 1.5 or so (I know, I'm ancient and old). But recently had to install Chromium because Firefox does not support something I "need".

This also isn't a forum for driving engagement to your fucking Reddit post.

KHTML will never be able to compete with the likes of Trident or Gecko! /s

They aren't entirely wrong - to give an example:

Stepmania 3.9 win32 still works fine on Windows 11, you run it, it works. It's not statically compiled either. It works on wine just as good.

Stepmania 3.9 for Linux i386 though - now you've got to comb through old libraries to get old, incompatible versions of libpng, libmad, sdl1.x, etc, you've got to set up multiarch, fumble around with sound too since it's expecting OSS or ALSA directly.

The windows version still 'justwerx' even on Linux under wine. The linux native version also works after a lot of faffing about.

They are wrong that an extra layer of abstraction would make this better. Just use .appimage with the libraries included. (though that wouldn't fix the sound issue)

At this point, it feels like I’m encountering the same arguments across different platforms.

If many people from different places are giving you similar feedback, maybe you need to reflect on that feedback, rather than just posting it somewhere else hoping for a different answer.

They are both declarative. The main difference is NixOS has the package build system built into its package management vs Microos which uses zypper and the Open Build System for package building.

Both have declarative config files you either activate via command or get automatically referenced on reboot.

For microos it both ignition, AND combustion.

I'll be honest though both have been a total pain in the ass (I say with love they are still opensource and Linux in the best of ways).

There is a tool kit for sle micro (and I assume microos too) called elemental that builds them from ContainerFile/DockerConfig files that just feels more sane to me. If it gets too complex for a containerfile I'm doing something wrong anyways imho. That said I do really like NixOS/Guix ability to have the dev build tool, package build tool, distro build tool, and sysadmin tool all be the same language.

What does it actually do?

Yeah that's a nice aspect to it, for sure. Like that band that took away all their music from Spotify in protest, King Gizzard And The Lizard Wizard.

You never know!

My girlfriend asked me to download her collection, too. She still didn't give up streaming, but knowing her favs will never be taken away from her gives her some peace of mind.

There's only two large differences from how you're currently using Firefox. The URL bar doesn't span the whole top of the window. But instead exist on the sidebar with the tabs. And the tabs can hide themselves automatically on the left to right side whichever side you have it moved to. Or you can have it always visible. I have mine set to autohide. And yeah the URL bar is the only thing that sometimes trips me up. When I want to check to see the URL I'm on or copy it I have to remember to go to that sidebar. But it really doesn't happen as often as I was worried it would.

I think KDE team maintains it, but I must admit I have no proof of such... it is just pure faith into them...

Yet should I have no choice between chromium and konqueror, I would take the second without even trying the first.

And I really loved konqueror before I became a gnome user... You can run konsole in konqueror, isn't that cool?

I mean, something’s only work on Chromium based browsers. (Lookin at you Keychron software)

I use Helium as my backup browser when I need a Chromium based browser, but considering this is a lib issue it probably isn’t exempt from this problem

Zen browser looks great but intimidating - feels like a lot of muscle memory to retrain.

I have swapped Firefox to vertical tabs that stay minimized and that cuts back on visual cutter pretty dramatically

It's nice that it is Webkit based but the interface isn't great; for example a lot of wasted space at the top due to the very old fashioned menu bar. Hopefully it will come in to line with other KDE software like Dolphin and move to a hamburger style menu? But regardless it is generally a little clunky and old fashioned.

I think realistically, Konqueror is just too small a project to be able to compete with Firefox or Chromium. It's great that it's maintained, but a little worrying that the last release was in May when internet security risks move very fast. I'm not sure I could in all conscience recommend it but I'm happy to be corrected if these concerns are misplaced?

Honestly lately I've been very into zen. Firefox based, Firefox extensions. But the UI gets out of the way. Allowing you a traditional F11 workflow, without a lot of the drawbacks. Hell even as a small window on the screen its great. Your website full window.

Have you tried Konqueror? It is one of KDE jewels... even if you may prefer other solutions, at least it is worth a try... (unlike google things)