pretty much any modern linux filesystem is gonna be significantly better and more advanced than ntfs
KDE's a little bit weirder about this because they really want distros to mirror upstream. This isn't going to work for any slow releasing distro unless they want to backport fixes. KDE devs basically abandon old versions.
I was thinking about this the other day. Someday soon the kernel is going to drop 32bit support and a lot of old driver code has been stripped. There won't be nearly as much support for 32bit stuff so it would make sense for everyone to consolidate into a few "retro distros".
KDE Neon is their testing distro that puts the very latest version of KDE on a stable Ubuntu base. This ensures you get the latest patches as soon as they are merged.
Ext4 is the filesystem for Linux. It's been extensively battle-tested over almost two decades and is all but guaranteed to be reliable.
ntfs3. For those curious: 71 seconds with defconfig, around 18 minutes with allmodconfig.
I believe they're roughly around the same technically/feature wise, ie. they're both journaling file systems. However ext4 is probably better at this point in time because I doubt microsoft has been putting any resources into NTFS in the past decade compared to continued ext4 support.
xfs is not a copy-on-write filesystem. It has some optional CoW features in constant development, but they're less battle-tested, and the filesystem isn't built to be CoW from the ground up (e.g., with metadata), so it will likely never be fully CoW however many new features are added.
Not a fan of ZFS? I wanted to do a ZFS on root Gentoo install, but it seemed not worth the effort for my use case. Apparently, from what I've been told, ZFS is only benefits from having multiple pools. Also, I read that it can cause a system freeze if you use it in conjunction with zram (at least that's what the Arch Linux wiki told me). And it can break with kernel updates because it needs an out of tree module that is very picky.
I have cp aliased to cp --reflink (although it's already set to --reflink=auto by default so any filesystem that supports COW will already be using reflink).
Where do you see this? They shouldn't interact (obviously keep zram away from your zfs pool)
Here. The Arch Linux wiki says using ZFS with swap can cause a system freeze because zvol uses memory intensive operations. I use a lot of zram as a replacement for swap because I noticed WINE games would freeze up my system consistently without any swap if I played any games for too long.
I don't like ZFS simply because as you mention it's not in the kernel and that causes issues with versioning. Like, does using an out of tree module that has specific kernel version requirements to mount your root FS while running a rolling release distro sound like an attractive proposition to you?
I used Neon for a while (it came with the laptop I bought for work). It was fine, until I had to upgrade to a newer version of the underlying ubuntu base and everything broke. I switched to MX after that.
There's a nice benefit to using XFS on Gentoo: it supports reflinks, while ext4 doesn't, so you get nice CoW when Portage merges packages to the live filesystem.
Dev snared in crypto phishing net, 18 npm packages compromised
Popular npm packages debug, chalk, and others hijacked in massive supply chain attack
Thomas Claburn
Mon 8 Sep 2025 // 19:06 UTC
Crims have added backdoors to at least 18 npm packages after developer Josh Junon inadvertently authorized a reset of the two-factor authentication protecting his npm account.
The malware targets cryptocurrency transactions on various blockchains such as Ethereum, Bitcoin, Solana, and Tron.
In posts to Bluesky and GitHub on Monday, Junon acknowledged that a phishing email had duped him, allowing miscreants to take over his account
At least he owned up to it. That's more than what most people would do.
